A linearly homomorphic signature method and system for zero-knowledge proofs of subset membership
The linearly homomorphic signature method with EIGamal ciphertexts and randomizable tags addresses the privacy and security challenges in electronic voting by enabling efficient and secure subset membership proofs, preventing vote manipulation and ensuring strong privacy and security in electronic voting systems.
Patent Information
- Application Number
- PCT/EP2024/062934
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-07-28
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-21
AI Technical Summary
Existing electronic voting systems face challenges in maintaining privacy and security, particularly in preventing vote-selling and coalition attacks, as they rely on trusted third parties and are vulnerable to malicious voters who may manipulate or reveal encrypted ballots.
A linearly homomorphic signature method and system for zero-knowledge proofs of subset membership using EIGamal ciphertexts with randomizable tags, which allows for efficient and secure proof of subset membership without revealing vote information, eliminating the need for a trusted third party and ensuring receipt-freeness and non-malleability.
The solution provides strong privacy and security by enabling constant-time, constant-size proofs of subset membership, preventing vote-selling and coalition attacks, and ensuring that only the voter can verify their own ballot, thus enhancing the integrity and secrecy of electronic voting systems.
Smart Images

Figure EP2024062934_21112024_PF_FP_ABST
Abstract
Description
[0001] A linearly homomorphic signature method and system for zero-knowledge proofs of subset membership
[0002]
[0001] Technical field
[0003]
[0002] The present invention relates to the technical field of cryptography. Particularly, the invention relates to the technical field of cryptography applied in various areas such as in electronic voting
[0004] 5 system, for example in an internet of things environment.
[0005]
[0003] Background of the invention
[0006]
[0004] With the all-digital society, and more recently with the pandemic and multiple lock-down periods, democracy is moving towards remote electronic voting, a.k.a. internet voting. Several solutions have been developed. They all encrypt the ballot on the voter-side to guarantee the voter’s privacy.
[0007] 10
[0005] Thereafter, several approaches exist for counting the tally, according to the complexity of the election. For example, one applies a mixing-network, which permutes and randomizes the encrypted ballots, before decryption of all the individual ballots to perform the counting in the clear, as one does with paper-based voting systems when one opens the envelops after having mixed them to remove any link with the voters.
[0008] 15
[0006] It seems therefore that electronic voting is one of the most interesting applications of modern cryptography, as it involves many innovative tools to guarantee several a priori contradictory security properties: the integrity of the tally and the privacy of the individual votes. While many efficient solutions exist for honest-but-curious voters, that follow the official procedure but try to learn more than just the public result, preventing attacks from malicious voters is much more
[0009] 20 complex: when voters may have incentive to send biased ballots, the privacy of the ballots is much harder to satisfy, whereas this is the crucial security property for electronic voting. The present invention solves at least some of these technical issues.
[0010]
[0007] Summary of the invention
[0011]
[0008] According to one aspect, the present invention relates to a linearly homomorphic signature method
[0012] 25 for zero-knowledge proofs of subset membership on at least one ciphertext, preferably at least one EIGamal ciphertext in a group (G with a generator P of prime order / ?, regarding at least one subset authorized plaintexts, said plaintexts being authorized by at least one authority device AUT, said cyphertext being generated from a plaintext taken among said subset 5, said method being executable by at least one computing system, preferably said computing
[0013] 30 system being communicatively connected to at least one communication network, said method using randomizable tags, said method comprising at least: o An initialization step, preferably executed by said authority device AUT using at least one initialization module IM, said initialization step comprising at least a generation step of at least:
[0014] 35 • one pair of EIGamal encryption keys (DK, EK) for plaintexts comprised by a group wherein the decryption key DK is generated as and the encryption key EK is generated as wherein z is the above
[0015] 1 private vector of scalars that defines the decryption key DK, and P is said generator of the group of prime order p;
[0016] • one pair of linearly homomorphic signature keys (SK, VK) for messages in said messages comprising at least ciphertexts;
[0017] 5 • N verifiable tags
[0018] • N pairs of signatures such as: wherein is configured to characterize a proof on a subset 5, preferably, where is a full-domain hash function into
[0019] 10 Said initialization step generating a set of public parameters comprising: o A ciphertext creation step with at least one proof of subset membership, preferably executed by at least one sender device SEND using at least one encryption module EM, said ciphertext creation step comprising the generation of at least one EIGamal ciphertext
[0020] 15 for at least one authorized plaintext for a given y, with a random scala such as: o A proof creation step, preferably executed by at least said sender device SEND using at least a first proof module PM1 , from Tag;- and for the above fixed y, comprising:
[0021] 20 • a first randomization step, preferably executed by said sender device SEND using at least a first randomization module RM1 , said first randomization step comprising a randomization of at least one Tag;- into Tag’, for said given y;
[0022] • a first computation step, preferably executed by said sender device SEND using at least a first computational module CM1 , of and wherein: is a valid
[0023] 25 signature of under VK for the tag Tag' and is a valid signature of a randomizer under VK for the tag Tag'; o A generation step, preferably executed by said sender device SEND using at least a generation module GM, comprising at least:
[0024] • generating a pair of linearly homomorphic signing-verification keys (sk, vk) for
[0025] 30 messages in
[0026] • generating signatures and wherein: o A sending step, preferably executed by said sender device SEND using at least a sending
[0027] 35 module SM, from the sender device SEND to at least one receiver device REC of the
[0028] 2 ciphertexts together with the proof comprising and with the signatures o A verification step, preferably executed by said receiver device REC using at least one verification module VM, said verification step comprising at least the verification of at least:
[0029] 5 • the validity of Tag';
[0030] • the validity of the signature under VK for the tag Tag', and the validity of the signature ( ) under VK for the tag Tag';
[0031] • the validity of the signatures on under vk and on under vk;
[0032] 10 o A second randomization step, preferably executed by said receiver device REC using at least a second randomization module RM2, of said EIGamal ciphertext to generate the ciphertext using a random scalar and a randomizer such as:
[0033] 15 o A second computation step, preferably executed by said receiver device REC using at least a second computational module CM2, of a signature being a valid signature of under VK for the tag Tag'; o A third computation step, preferably executed by said receiver device REC using at least
[0034] 20 said computational module CM2, of a signature a : wherein a is a valid signature of under vk; o A second proof creation step, preferably executed by at least said receiver device REC using at least a second proof module PR2, of a proof from said proof
[0035] 25 comprising:
[0036] • a third randomization step by at least said second randomization module RM2 of the tag Tag' into Tag" ;
[0037] • a fourth computation step by at least said second computational module CM2 of the signature into being a valid signature of under VK for the
[0038] 30 tag Tag"; o A storing step, preferably executed by the receiver device REC using at least a storing module STM, of the ciphertext together with said proof comprising and with the signature which are configured to be publicly verified and wherein:
[0039] • Tag" is a valid tag;
[0040] 35 • is a valid signature on under VK for the tag Tag" allowing to prove that the plaintext is in the subset
[0041] 3 • is a valid signature on under vk.
[0042]
[0009] The present invention uses advantageously linearly homomorphic signatures to design short and efficient homomorphic proofs of subset membership on EIGamal ciphertexts. But contrarily to the prior art, that were using signatures on randomizable ciphertexts just for allowing randomization on
[0043] 5 the server-side, and thus for achieving receipt-freeness for a mixnet-based system that can check the validity of the ballots in the clear, the present invention additionally uses signatures on randomizable ciphertexts on the client-side, from multiple signatures generated at the setup phase, by the electoral board, i.e. the authority device AUT, to derive efficient proofs of valid ballots, in their encrypted form. One proof of subset membership has a constant size and takes a constant
[0044] 10 time for generation, whatever the size of the subset. The present invention avoids the need of a trusted third party, in the case where the signing-verification keys and the signatures can be efficiently generated in a distributed way, for example.
[0045]
[0010] The present invention uses tag-based signatures, where the tags target the vector sub-spaces, but still being randomizable and unlinkable, as in, to keep privacy of the ciphertexts. Signatures for
[0046] 15 proofs can only be generated for valid ballots, without revealing any information about the votes. Therefore, the present invention uses full-fledge linearly homomorphicsignatures with tags, to have multiple vector sub-spaces, that cannot be combined and additional properties to make signatures unlinkable, whichever is the vector sub-space.
[0047]
[0011] Using zero-knowledge proofs, the present invention allows to prove that some specific properties
[0048] 20 are satisfied by the text in the clear, without revealing any additional information.
[0049]
[0012] The present invention allows a higher level of privacy. The present invention is particularly well designed to be applied in a situation wherein the voters are maybe not all honest. Indeed, voters might deviate from the honest behaviour, for multiple reasons. Some might even be ready to change their votes for money or to break privacy. Then, the present invention allows more
[0050] 25 advanced protections to really achieve a high privacy level.
[0051]
[0013] For example, the present invention protects the voting system against a coalition of voters that really wants to know the vote of a determined person. Even if they try to duplicate her encrypted ballot and cast it in their names, the present invention blocks them to get the vote of said determined person. To avoid such an attack, also called a CS-attack see for example the following publication
[0052] 30 “Veronique Cortier and Ben Smyth. Attacking and Fixing Helios: An analysis of Ballot Secrecy. CSF 2011 : 297-311.’’, the present invention can use some non-malleability features, as discussed hereafter.
[0053]
[0014] Vote-selling is another major threat, when some voters may have strong incentive, with a reward or external pressures, to vote for someone when being able to prove it. Actually, any technique that
[0054] 35 encrypts the ballot on the client-side, without any modification before storing it in the public ballot- box, is subject to vote-selling attacks, see for example the following publication “J. C. Benaloh and D. Tuinstra. Receipt-Free Secret-Ballot Elections. STOC 1994.’’, and even at high scale: the clientside code can always be patched in order to reveal the randomness used during encryption, as a receipt to convince anybody of the content of the vote. The present invention allows to avoid vote¬
[0055] 40 selling, also called a VS-attack. For example, by randomizing encrypted ballots before storage, the present invention prevents such an attack.
[0056] 4
[0015] The approach followed by the present invention excludes VS-attacks and is compatible with other improvements: the voter can use a one-time linearly homomorphic signature to trace and check his vote after randomization, and append a single Groth-Sahai Diffie-Hellman proofto avoid CS-attack as discussed further in the description. This provides strong receipt-freeness.
[0057] 5
[0016] The present invention relates also to a computer program product which, when executed on at least one processor unit, executes the method according to the present invention.
[0058]
[0017] The present invention relates also to a non-volatile memory comprising at least one computer program product according to the present invention.
[0059]
[0018] The present invention relates also to a voting system configured to execute the method according
[0060] 10 to the present invention, said system comprising at least: a. One authority device AUT comprising at least one initialization module IM, said initialization module IM being configured to execute said initialization step. b. One sender device SEND comprising at least:
[0061] An encryption module EM being configured to execute said ciphertext creation
[0062] 15 step. ii. A first proof module PM1 being configured to execute said proof creation step. Said first proof module PM1 comprising at least: o A first randomization module RM1 being configured to execute said first randomization step;
[0063] 20 o A first computational module CM1 being configured to execute said first computation step. iii. A generation module GM being configured to execute said generation step; iv. A sending module SM being configured to execute the sending step, and advantageously to communicate with at least one receiver device REC.
[0064] 25 c. One receiver device REC comprising at least:
[0065] A verification module VM being configured to execute said verification step; ii. A second randomization module RM2 being configured to execute said second randomization step, and the third randomization step; iii. A second computational module CM2 being configured to execute said second
[0066] 30 computational step, said third computational step and said fourth randomization step; iv. A second proof module PM2 being configured to execute said second proof creation step, said proof module comprising at least: o a second randomization module RM2;
[0067] 35 o a second computational module CM2; v. A storing module STM being configured to execute said storing step.
[0068]
[0019] The present invention relates also to a use of the voting system according to the present invention.
[0069]
[0020] Before providing below a detailed review of embodiments of the invention, some optional characteristics that may be used in association or alternatively will be listed hereinafter:
[0070] 40
[0021] According to an example, the pair of linearly homomorphic signing-verification keys (sk,vk) for messages in are generated, in a type III pairing-friendly setting , where
[0071] 5 and are two groups of prime order p, spanned by P and respectively, equipped with a pairing application e into the target group such as:
[0072]
[0022] According to an example, in a bilinear setting the pair of linearly homomorphic
[0073] 5 signing-verification keys (sk,vk) for messages in are generated such as:
[0074]
[0023] According to an example, in a bilinear setting the signatures and are generated such as:
[0075] 10
[0076]
[0024] According to an example, four random points are generated and appended to the public parameters, preferably for the Groth-Sahai proofs, advantageously in a bilinear setting
[0077] 15
[0025] According to an example, the proof from Tag;- and is generated such as:
[0078] Wherein is a valid signature of under VK for the tag and wherein is a valid signature of the randomizer under VK for the tag
[0079] 20
[0026] According to an example, the generation step comprises generating a Diffie-Hellman value ( ) and generating a Groth-Sahai proof of Diffie-Hellman tuple for
[0080]
[0027] According to an example, the sending step from the sender device SEND to the receiver device REC comprises the sending of the value W and of the proof
[0081] 25
[0028] According to an example, the verification step comprises the verification of the validity of the signature such as is a valid signature on under vk;
[0082]
[0029] According to an example, the verification step comprises the verification of the validity of the signatures on under vk and on under vk;
[0083]
[0030] According to an example, the verification step comprises the verification of the validity of the Diffie-
[0084] 30 Hellman proof on the tuple
[0085]
[0031] According to an example, the randomizer is equal to such as wherein P is the generator of and is the public encryption key;
[0086] 6
[0032] According to an example, the randomization of said EIGamal ciphertext to generate the ciphertext using a random scalar is such as:
[0087]
[0033] According to an example, the second computation step comprises a computation of the randomized
[0088] 5 Groth-Sahai proof being a valid Diffie-Hellman proof on the tuple using
[0089]
[0034] According to an example, the storing step comprises the storing of
[0090]
[0035] According to an example, the pair of linearly homomorphic signing-verification keys SK and VK are generated such as
[0091] 10
[0036] According to an example, the N verifiable tags Tagy are generated such as with with their validity proofs
[0092]
[0037] According to an example, the N pairs of signatures, for are generated such as:
[0093] 15
[0094]
[0038] According to an example, Doand D are equal to: with a random scalar
[0095]
[0039] According to an example, the proof PRSis generated, from Tagy and such as:
[0096] 20
[0097] Wherein 2'0is a valid signature of ( ) under VK for the tag go( ) • Tag and wherein 2\ is a valid signatures o f under VK for the tag
[0098]
[0040] According to an example, the generation step comprises the generation of Diffie-Hellman values togetherwith Groth-Sahai proofs (com, proof) of
[0099] 25 Diffie-Hellman tuple for (P, Co, H, W) and of Diffie-Hellman tuple for ;
[0100]
[0041] According to an example, the sending step from the sender device SEND to the receiver device REC comprises the sending of the proof comprising , and
[0101]
[0042] According to an example, the verification step comprises verifying that:
[0102] • the tags Tag'oand Tag', are valid;
[0103] 30 • the signature 0is valid on the message and tag under VK;
[0104] • the signature is valid on the message and tag Tag', under VK;
[0105] • the signature is valid on the message under vk;
[0106] • the signature is valid on the message under vk;
[0107] 7 • the Diffie-Hellman proofs is valid on the tuples and is valid on the tuples
[0108]
[0043] According to an example, the third randomization step of the tags \ into is such as:
[0109] 5
[0110]
[0044] According to an example, the fourth computation step of the signatures and is such as:
[0111]
[0045] According to an example, the second computation step comprises a computation of the randomized Groth-Sahai proof of Diffie-Hellman tuple for using and s.
[0112] 10
[0046] According to an example, the storing step comprises the storing of ( )
[0113]
[0047] According to an example, the N verifiable tags Tag; are generated such as
[0114]
[0048] According to an example, the N pairs of signatures, for are generated such as:
[0115] 15
[0116]
[0049] According to an example, the randomization of at least for a random is such as:
[0117] 20
[0050] According to an example, the computation of and into and respectively, is such as:
[0118]
[0051] According to an example, the randomizer is equal to the signatures and such as:
[0119] 25
[0120]
[0052] According to an example, the verification step comprises the verification of the following equalities:
[0121] 8 5
[0122] 10 which are signatures of and of respectively, under VK for said tag Tagy.
[0123]
[0058] According to an example, one among the authority device AUT, the sender device SEND and the receiver device REC is taken among: a robot, a smartphone, an Internet of Thing device, an artificial intelligence.
[0124]
[0059] Brief description of the drawings
[0125] 15
[0060] The aims, objects, as well as the technical features and advantages of the invention will emerge better from the detail description of an embodiment of the invention which is illustrated by the following figures in which:
[0126] Figure 1 is a general schematic view of an embodiment of the present invention.
[0127] Figure 2 is a schematic view of a method according to an embodiment of the present invention.
[0128] 20 Figure 3 is a schematic view of a system according to an embodiment of the present invention.
[0129] Figure 4 is a schematic view of an example of implementation of the present invention.
[0130]
[0061] The drawings are given by way of example and do not limit the invention. They constitute representations of principle intended to facilitate understanding of the invention and are not necessarily on the scale of practical applications.
[0131] 25
[0062] Detailed description
[0132]
[0063] The examples and conditional language recited herein are principally intended to aid the reader in understanding the principles of the present invention and not to limit its scope to such specifically recited examples and conditions. It will be appreciated that those skilled in the art may devise various arrangements which, although not explicitly described or shown herein, nonetheless
[0133] 30 embody the principles of the present invention and are included within its spirit and scope.
[0134]
[0064] Furthermore, as an aid to understanding, the following description may describe relatively simplified implementations of the present invention. As persons skilled in the art would understand, various implementations of the present technology may be of a greater complexity.
[0135]
[0065] Moreover, all statements herein reciting principles, aspects, and implementations of the present
[0136] 35 invention, as well as specific examples thereof, are intended to encompass both structural and
[0137] 10 functional equivalents thereof, whether they are currently known or developed in the future. Thus, for example, it will be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative circuitry embodying the principles of the present invention. Similarly, it will be appreciated that any flowcharts, and the like represent various processes which
[0138] 5 may be substantially represented in computer-readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
[0139]
[0066] The functions of the various elements shown in the figures, including any functional block labeled as a "processor" or “module", may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided
[0140] 10 by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. In some embodiments of the present invention, the processor may be a general-purpose processor, such as a central processing unit (CPU), for example. Moreover, explicit use of the term a "processor" should not be construed to refer exclusively to hardware capable of executing software, and may
[0141] 15 implicitly include, without limitation, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read-only memory (ROM) for storing software, random access memory (RAM), and non-volatile storage. Other hardware, conventional and / or custom, may also be included.
[0142]
[0067] Software modules, or simply modules which are implied to be software, may be represented herein
[0143] 20 as any combination of flowchart elements or other elements indicating performance of process steps and / or textual description. Such modules may be executed by hardware that is expressly or implicitly shown. Moreover, it should be understood that module may include for example, but without being limitative, computer program logic, computer program instructions, software, stack, firmware, hardware circuitry or a combination thereof which provides the required capabilities.
[0144] 25
[0068] The present disclosure is here described in detail with reference to non-limiting embodiments illustrated in the drawings.
[0145]
[0069] The present invention relates preferably to a new technique to prove that a ciphertext, preferably an EIGamal ciphertext, contains a message from at least one specific subset 5, advantageously using linearly homomorphic signatures and tags. As it will be described, the proofs provided by the
[0146] 30 present invention are both quite efficient to generate, allowing the use of low-power devices to vote, and randomizable, which can be important for the strong receipt-freeness property. The present invention is well-suited to prevent vote-selling and replay attacks, which are the main threats against the privacy in electronic voting.
[0147]
[0070] Before describing in more details, the present invention, some computational assumption will be
[0148] 35 presented hereafter.
[0149]
[0071] For the development and security analysis of the present invention, the Generic Group Model (GGM) and the Algebraic Group Model (AGM), see for example the following publications “Victor Shoup. Lower Bounds for Discrete Logarithms and Related Problems. EUROCRYPT 1997: 256- 266." and “Georg Fuchsbauer, Eike Kiltz, Julian Loss. The Algebraic Group Model and its
[0150] 40 Applications. CRYPTO (2) 2018: 33-62.", have been used, where the adversary can make generic operations on the group and pairing evaluations. Hence, any new generated group element comes as a linear combination of the input group elements. The former GGM being a slightly stronger 11 model than the latter AGM, as encodings of group elements can even be chosen at random. But in both cases, any group element provided by the adversary comes with the explicit coefficients of the linear combination of the input elements. This will provide the simulation extractability of the proofs generated by the present invention. The following classical assumptions in a group of
[0151] 5 prime order for any generator is used: a. Discrete Logarithm (DL) Assumption: Given it is computationally hard to recover b. Decisional Diffie-Hellman (DDH) Assumption: For distributions are computationally hard to distinguish;
[0152] 10 c. Square Discrete Logarithm (SDL) Assumption: Given it is computationally hard to recover x; d. Decisional Square Diffie-Hellman (DSDH) Assumption: For distributions are computationally hard to distinguish. e. The SXDH assumption claims that the DDH assumption holds in both groups G and G, when
[0153] 15 we are in a type III pairing-friendly setting
[0154]
[0072] On a high level, an EIGamal ciphertext encrypts a plaintext, seen as a vector encoded as under the encryption key From the linear property of the EIGamal encryption scheme (see for example the following publication “Taher El Gamal. A Public Key Cryptosystem and a Signature Scheme Based on Discrete Logarithms.
[0155] 20 CRYPTO 1984: 10-18"), can be transformed into for any matrix A, to get a ciphertext under the encryption The matrix A can be a projection matrix, such as A - (1,0, ... ,0), to select one component of As an example, the subset can be to enforce bit values. The matrix A can be a sum matrix, such as A - (1, ... ,1), to sum the component of The subset can then be a larger range The subset can be any
[0156] 25 list of specific vectors that specifies the admissible votes of length n. By abuse of notation, the plaintexts are either the vectors of scalars or their encodings Multiple matrices A and multiple subsets can be used simultaneously on the same EIGamal ciphertext for more complex proofs, with multiple proofs of subset membership and
[0157] 30
[0073] According to the present invention, first an authority device AUT generates linearly homomorphic signatures under a verification key VK on all the possible trivial ciphertexts of as well as on the encryption key: the signatures under the common tag Then, preferably, for any choice ;, a random combination of the two signatures (with coefficient 1 for the former), leads to a valid signature under VK on a ciphertext of Mj: where
[0158] 35 is a valid signature on under the tag Preferably, the first components and later checked with respect to for , implies the coefficient 1 on in the combination. One can also keep as a valid signature on the randomizer underthe tag forfurther randomization.
[0159] 12
[0074] According to an embodiment, whereas the ciphertexts do not reveal information about j, under the DDH assumption (EIGamal encryption), the signatures are valid under only, which reveals j. Hence the need of randomizable tags to make the new tag r and the new signatures unlinkable to and This is one of the main
[0160] 5 features of the present invention, which provides the first constant generation-time and constant proof-size for randomizable zero-knowledge proof of subset membership.
[0161]
[0075] As described in the following, are modified before sending them to keep vote- privacy, thanks to the property of randomizable tags.
[0162]
[0076] As described hereafter, several embodiments of the present invention can be used.
[0163] 10
[0077] The present invention can use, according to an embodiment, the FHS signature (see for example the following publication “Georg Fuchsbauer, Christian Hanser, Daniel Slamanig. Structure- Preserving Signatures on Equivalence Classes and Constant-Size Anonymous Credentials. J. Cryptol. 32(2): 498-546.“) forthe Linearly homomorphic Signatures with Randomizable Tags (LH- Sign-RTag), for example in a type III pairing-friendly setting , also presented as
[0164] 15 a signature on randomizable ciphertexts : a tag is ) for a scalar the signature of under VK that can both be verified by . Using this approach, one can randomize and compute the signature in a perfectly unlinkable way. Hence, the privacy relies on the EIGamal encryption scheme only. From a Common Reference String (CRS) of linear length
[0165] 20 in the size of the subset (with the for all the proofs of subset membership are thereafter both size and time efficient (independent of the size of as the voter only has to generate a ciphertext for appropriate and to randomize keeping unchanged. According to another embodiment, the present invention can use the SDH signature (see for example the following publication “Chloe Hebant, David Pointcheval. Traceable
[0166] 25 Constant-Size Multi-authority Credentials. SCN 2022: 411-434."), with Square Diffie-Hellman tags
[0167]
[0078] According to a preferred embodiment, the present invention uses Linearly homomorphic Signatures with Randomizable Tags (LH-Sign-RTag) for zero-knowledge proofs of subset membership on EIGamal ciphertexts. The present invention can also use One-Time Linearly homomorphic
[0168] 30 Signature (OT-LH-Sign).
[0169]
[0079] According to some embodiments, additional, but optional, steps to make them non-malleable and traceable by the prover are possible and will be described hereafter. Then, combinations of such proofs can be used for any kind of election, to prove the validity of at least one ballot, preferably with randomizability to provide receipt-freeness, i.e. to exclude VS-attacks, and / or non-malleability
[0170] 35 to provide the strong receipt-freeness, i.e. to exclude CS-attacks.
[0171]
[0080] According to an embodiment and as illustrated by figures 1 to 4, the present invention relates to a method 100. Said method 100 involves at least preferably: a. an authority device AUT 10, said authority device AUT 10 is configured to generate at least a set of public parameters, said authority device AUT 10 can be distributed among several
[0172] 40 parties;
[0173] 13 b. a sender device SEND 20, Said sender device SEND 20 is configured to generates at least one ciphertext with at least one proof of subset membership, preferably with at least one non-malleable proof of subset membership; c. a receiver device REC 30, said receiver device REC 30 is configured to store at least one
[0174] 5 final ciphertext, preferably to randomize and / or store at least one final ciphertext.
[0175]
[0081] As described hereafter, a pairing-friendly setting is used, where the SXDH assumption holds, for the EIGamal encryption privacy.
[0176]
[0082] The present invention considers at least one set of the authorized plaintexts, and denote an element that characterizes the proof on (in case of multiple concurrent
[0177] 10 proofs, on the same ciphertext). It can be where is a full-domain hash function into Advantageously, is configured to characterize at least one proof on the subset as described hereafter.
[0178]
[0083] According to an embodiment, the present invention relates to a linearly homomorphic signature method for zero-knowledge proofs of subset membership on at least one EIGamal ciphertext
[0179] 15 regarding at least one subset authorized plaintexts. Preferably, said plaintexts are authorized by at least said authority device AUT 10. Said cyphertext is advantageously generated from a plaintext taken among said subset
[0180]
[0084] Said method is configured to be executable by at least one computing system. Preferably said computing system is communicatively connected to at least one communication network.
[0181] 20
[0085] Advantageously, and as described hereafter, said method 100 uses randomizable tags.
[0182]
[0086] According to an embodiment, said method 100 comprising at least: a. An initialization step 101 , preferably executed by said authority device AUT 10, preferably using at least one initialization module IM 11 . Said initialization step 101 comprises at least a generation step of at least:
[0183] 25 one pair of EIGamal encryption keys (DK, EK) for plaintexts comprised by a group , and wherein, preferably, the decryption key DK is generated as and the encryption key EK is generated as ii. one pair of linearly homomorphic signature keys (SK, VK) for messages in said messages comprising at least ciphertexts;
[0184] 30 iii. N verifiable tags for j iv. N pairs of signatures such as:
[0185] Said initialization step 101 generating at least a set of public parameters comprising:
[0186] 35 b. A ciphertext creation step 102, preferably with proof of subset membership, preferably executed by at least said sender device SEND 20 using at least one encryption module EM 21 . Said ciphertext creation step 102 comprises preferably the generation of at least
[0187] 14 one EIGamal ciphertext ) for at least one authorized plaintext for a given with a random scalar such as: c. A proof creation step 103, preferably executed by at least said sender device SEND 20
[0188] 5 using at least a first proof module PM1 22, of at least one proof from comprising at least: i. A first randomization step, preferably executed by at least a first randomization module RM1 23. Said first randomization step comprises at least a randomization of at least one into for a given
[0189] 10 ii. A first computation step, preferably executed by at least a first computational module CM1 24, of , wherein: is a valid signature of under VK for the tag and is a valid signature of a randomizer under VK for the tag d. A generation step 104, preferably executed by at least said sender device SEND 20 using
[0190] 15 at least a generation module GM 25, comprising at least: i. Generating at least a pair of linearly homomorphic signing-verification keys (sk, vk) for messages in ; According to an embodiment, the pair of linearly homomorphic signing-verification keys (sk,vk) for messages in are generated such as:
[0191] 20 ii. Generating at least signatures wherein: e. A sending step 105, preferably executed by at least said sender device SEND 20 using at
[0192] 25 least a sending module SM 26, from the sender device SEND 20 to at least one receiver device REC 30, of the ciphertexts together with the proof and with the signatures . Said proof comprises preferably at least f. A verification step 106, preferably executed by said receiver device REC 30 using at least one verification module VM 31 . Said verification step 106 comprises at least the verification
[0193] 30 of at least: i. the validity of the tag Tag' ii. the validity of the signature ( ) under VK for the tag and the validity of the signature , under VK for the tag Tag'; iii. the validity of the signatures ) under vk and on under
[0194] 35 vk;
[0195] 15 g. A second randomization step 107, preferably executed by at least said receiver device REC 30 using a second randomization module RM2 32, of said EIGamal ciphertext to generate the ciphertext using a random scalar and a randomizer such as:
[0196] 5 h. A second computation step 108 of a signature preferably executed by at least said receiver device REC 30 using a second computational module CM2 33:
[0197] Advantageously is a valid signature of under VK for the tag
[0198] 10 i. A third computation step 109 of a signature , preferably executed by at least said receiver device REC 30 using a second computational module CM2 33:
[0199] Advantageously, is a valid signature of under vk; j. A second proof creation step 110, preferably executed by at least said receiver device REC
[0200] 15 30 using at least a second proof module PM2 34, of a proof from said proof comprising at least:
[0201] I. A third randomization step, preferably executed by the second randomization module RM2 32, of the tag ii. A fourth computation step, preferably executed by the second computational
[0202] 20 module CM2 33, of the signature being a valid signature of under VK for the tag k. A storing step 111 , preferably executed by at least said receiver device REC 30 in a storing module STM 35, of the ciphertext together with said proof comprising and with the signature which are configured to be publicly verified and
[0203] 25 wherein:
[0204] I. is a valid tag; ii. " is a valid signature on under VK for the tag allowing to prove that the plaintext is in the subset iii. is a valid signature on under vk.
[0205] 30
[0087] According to an embodiment, and in a bilinear setting a. The pair of linearly homomorphic signing-verification keys (sk,vk) for messages in are generated such as: b. The signatures are generated such as:
[0206] 16
[0207]
[0088] According to said embodiment, in the initialization step 101 , the authority device AUT 10 generates at least:
[0208] 5 a. Encryption Keys: A pair of EIGamal encryption keys (DK, EK) for messages in the decryption key is and the encryption key is b. Signature Keys: A pair of LH-Sign-RTag signing-verification keys (SK, VK) for messages in c. Verifiable Tags: N verifiable tags T
[0209] 10 d. Initial Signatures: N pairs of signatures
[0210]
[0089] Therefore, at the end of said initialization step 101 , public parameters are generated. Said public parameters comprise EK,VK, and
[0211]
[0090] Then, according to said embodiment, the ciphertext, preferably with proof of subset membership,
[0212] 15 creation step 102 is executed by said sender device SEND 20. Said sender device SEND 20 is configured to: a. Generate at least one ciphertext: The EIGamal ciphertext for his authorized plaintext with a random scalar
[0213] 20 b. Generate at least one proof of subset membership: the proof , from which are valid signatures of ( ) ( ) under VK for the tag Thanks to the property of LH-Sign-RTag, with randomizable tags, Tag can be randomized into Tag' and can be adapted, i.e. computed, into and respectively:
[0214] 25 and are valid signatures of respectively, under VK for the tag Tag'. c. Optionally, allow individual verifiability (for further randomization): A pair of OT-LH-Sign signing-verification keys (sk,vk) for messages in and the signatures and such as:
[0215] 30 d. Optionally, allow non-malleability: The Diffie-Hellman value ( ) , together with a Groth-Sahai proof of Diffie-Hellman tuple for (P, C0,H, W).
[0216]
[0091] The sender device SEND 20 then outputs the ciphertext ( ), together with the proof that
[0217] 35 consists of and optionally the signatures
[0218]
[0092] Then, the receiver device REC 30 is configured to:
[0219] 17 a. Optionally, before storing the ciphertext, randomize said ciphertext, after having verified all the values ( ) b. Verify all these values, such as, for example: i. the validity of Tag'
[0220] 5 II. the validity of the signatures respectively, under VK for the tag Tag'; ill. the validity of the signatures and on respectively, under vk; iv. the validity of the Diffie-Hellman proof it on the tuple
[0221] 10
[0093] The receiver device REC 30 is also configured to randomize the EIGamal ciphertext using a random scalar
[0222]
[0094] The receiver device REC 30 is also configured to compute, i.e. adapt, signatures:
[0223] 15 Preferably, is a valid signature of under VK for the tag Tag', and is a valid signature of under vk. Thanks to the property of LH-Sign-RTag, with randomizable tags, Tag' can be randomized into Tag" and ' can be computed, i.e. adapted, into is a valid signature of under VK for the tag Tag".
[0224]
[0095] The receiver device REC 30 can also compute the randomized Groth-Sahai proof
[0225] 20 s • H, using s and
[0226]
[0096] The receiver device REC 30 is configured to store the ciphertext ( ), together with the proof that consists of the signature , and which can be publicly verified: a. Tag" is a valid tag; b. is a valid signature on under VK for the tag Tag". This proves the plaintext
[0227] 25 must be in c. is a valid signature on under vk. This ensures the sender that contains the same plaintext as his initial ciphertext ), but without knowing the actual randomness, which exclude VS-attacks; d. is a valid Diffie-Hellman proof on the tuple This ensures that only
[0228] 30 the owner of vk can have initiated the ciphertext, which excludes malleability or repetition, and thus CS-attacks.
[0229]
[0097] According to an embodiment, four random points are generated and appended to the public parameters, preferably for the Groth-Sahai proofs.
[0230]
[0098] According to an embodiment, the proof , from is generated such as:
[0231] 35
[0232] Wherein is a valid signature of under VK for the tag and wherein is a valid signature of under VK for the tag
[0233] 18
[0099] According to an embodiment, the generation step 104 comprises generating a Diffie-Hellman value
[0234]
[0100] According to an embodiment, the generation step 104 comprises generating a Groth-Sahai proof of Diffie-Hellman tuple for (P, Co, H, W).
[0235] 5
[0101] According to an embodiment, the sending step 105 from the sender device SEND 20 to the receiver device REC 30 comprises the sending of the value W and of the proof
[0236]
[0102] According to an embodiment, the verification step 106 comprises the verification of the validity of the signature a such as is a valid signature on ) under vk allowing the sender device SEND 20 to know that contains the same plaintext as its initial ciphertext but
[0237] 10 without knowing the actual randomness, which excludes VS-attacks.
[0238]
[0103] According to an embodiment, the verification step 106 comprises the verification of the validity of the signatures under vk and on under vk.
[0239]
[0104] According to an embodiment, the verification step 106 comprises the verification of the validity of the Diffie-Hellman proof on the tuple
[0240] 15
[0105] According to an embodiment, the randomizer is equal to such as wherein P is the generator of and is the public encryption key.
[0241]
[0106] According to an embodiment, the randomization of said EIGamal ciphertext ) to generate the ciphertext using a random scalar is such as:
[0242] 20
[0107] According to an embodiment, the second computation step 108 comprises a computation of the randomized Groth-Sahai proof , being a valid Diffie-Hellman proof on the tuple using to s and
[0243]
[0108] According to an embodiment, the storing step 111 comprises the storing of
[0244]
[0109] According to another embodiment, the present invention can use FHS LH-Sign-RTag (for
[0245] 25 Fuchsbauer-Hanser-Slamanig, see for example the following publication “Georg Fuchsbauer, Christian Hanser, Daniel Slamanig. Structure-Preserving Signatures on Equivalence Classes and Constant-Size Anonymous Credentials. J. Cryptol. 32(2): 498-546.“). According to said embodiment, the present invention uses tags of the form for a scalar . Advantageously, it is self-verifiable as one ca n check that wherein
[0246] 30 e(Q, Q) is a pairing function between two elements of the two groups The signature of
[0247]
[0110] Preferably, one can easily randomize Tag and adapt, i.e. compute, the signature ) in a perfectly unlinkable way:
[0248] 35
[0249]
[0111] As the tags are self-verifiable tags, according to said embodiment, this approach is quite efficient, from both the computation and communication points of view.
[0250]
[0112] Preferably, the initialization step 101 is not distributed among multiple users or authorities. Advantageously, the verifiable tags and / or the initial signatures are generated on at least one
[0251] 40 secure device, i.e. one authority device AUT 10.
[0252]
[0113] According to said embodiment, called the FHS embodiment, the authority device AUT 10 is configured to generate:
[0253] 19
[0117] Then, according to said embodiment, the receiver device REC 30 is configured to: a. Before storing the ciphertext, randomize said ciphertext, after having verified all the values and such as:
[0254] 5 e and the validity of the Diffie-Hellman proof - (com, proof) on the tuple
[0255] 10 b. Randomize the EIGamal ciphertext using a random scalar c. Compute the signatures and randomize the tag, with such as:
[0256] 15 d. Compute the randomized Groth-Sahai proof for W' - W + s • H, using s and e. Store the ciphertext together with the proof that consists of the signature (vk, cr), and , which can be publicly verified.
[0257]
[0118] According to said embodiment, the N verifiable tags are generated such as
[0258] 20
[0259]
[0119] According to said embodiment, the N pairs of signatures, for are generated such as:
[0260]
[0120] According to said embodiment, the randomization of at least for
[0261] 25 a random is such as:
[0262]
[0121] According to said embodiment, the computation of and Ztinto respectively, is such as:
[0263] 21
[0122] According to said embodiment, embodiment, the randomizer is equal to ( such as wherein P is the generator of is the public encryption key. The signatures and are such as:
[0264] 5
[0265]
[0123] According to said embodiment, the verification step comprises the verification of the following equalities:
[0266] 10 wherein is a pairing function between two elements of the two groups and and the validity of the Diffie-Hellman proof (com, proof) on the tuple
[0267] 15
[0124] According to said embodiment, the third randomization step of the tag Tag' into is such as:
[0268]
[0125] According to said embodiment, the second computation step of the signatures being a valid signature of under VK for the tag Tag", is such as:
[0269] 20
[0270]
[0126] According to said embodiment, the second computation step comprises a computation of the randomized Groth-Sahai proof for , using s and
[0271]
[0127] According to said embodiment, the storing step 111 by the receiver device REC 30 in a storing module STM 35 comprises the storing of
[0272] 25
[0128]
[0273]
[0129] Preferably, for Groth-Sahai proofs (see for example the following publication “Jens Groth, Amit Sahai. Efficient Non-interactive Proof Systems for Bilinear Groups. EUROCRYPT 2008: 415-432”), one needs a random tuple and the proof (com, proof), consists of a
[0274] 30 commitment com of the secret witness known by the prover, and a proof proof, both being additively homomorphic, and publicly verifiable. The properties and the computations forthose proofs will not be described, as it is well known by the skilled person in the art.
[0275] 22 respect to (Hs, C'0, C') under vk. This implies (C'o, C') can only be a randomization of the initial ciphertext (C0, C): Mk- M}-, under the unforgeability of the OT-LH-Sign, as vk is ephemeral and used only once. This individual verifiability convinces all the voters ofthe integrity of the ballot-box, with the presence of their votes.
[0276] 5
[0177] According to an embodiment, the present invention relates to an electronic voting system. Said electronic voting system comprise at least an authority device AUT 10, a sender device SEND 20 and a receiver device REC 30.
[0277]
[0178] Said authority device AUT 10 comprises at least one initialization module IM 1 1. Said initialization module IM 11 is configured to execute said initialization step.
[0278] 10
[0179] Said sender device SEND 20 comprises at least: a. An encryption module EM 21 , preferably configured to execute said ciphertext creation step 102. b. A first proof module PM1 22, preferably configured to execute said proof creation step 103. Said first proof module PM1 22 comprising at least:
[0279] 15 I. A first randomization module RM1 23, preferably configured to execute said first randomization step; ii. A first computational module CM1 24, preferably configured to execute said first computation step. c. A generation module GM 25, preferably configured to execute said generation step 104;
[0280] 20 d. A sending module SM 26, preferably configured to execute the sending step 105, and advantageously to communicate with at least the receiver device REC 30, preferably using at least one communication network.
[0281]
[0180] Said receiver device REC 30 comprises at least: a. A verification module VM 31 , preferably configured to execute said verification step 106;
[0282] 25 b. A second randomization module RM2 32, preferably configured to execute said second randomization step 107, the third randomization step, and said fourth randomization step; c. A second computational module CM2 33, preferably configured to execute said second computational step 108, said third computational step 109; d. A second proof module PM2 34, preferably configured to execute said second proof
[0283] 30 creation step. Advantageously, said second proof module PM2 34 comprising at least:
[0284] I. Said second randomization module RM2 32; ii. Said second computational module CM2 33. e. A storing module STM 35, preferably configured to execute the storing step 1 11.
[0285]
[0181] According to an embodiment, the authority device AUT 10 can be an electronic device comprising
[0286] 35 a user interface. Said user interface being configured to allow a user to control the authority device AUT 10.
[0287]
[0182] According to an embodiment, the authority device AUT 10 can be a robot, preferably said robot being part of an Internet of Things environment and advantageously being configured to cooperate with other robots or computers.
[0288] 40
[0183] According to an embodiment, the authority device AUT 10 can be an artificial intelligence configured to cooperate with robots and / or computers and / or other artificial intelligences.
[0289]
[0184] According to an embodiment, the authority device AUT 10 can comprise at least one processor, and preferably at least one non-volatile memory. Said processor is advantageously configured to execute the steps executed by the authority device AUT 10.
[0290] 30
[0185] According to an embodiment, the sender device SEND 20 can be an electronic device comprising a user interface. Said user interface being configured to allow a user to vote.
[0291]
[0186] According to an embodiment, the sender device SEND 20 can be a robot, preferably said robot being part of an Internet of Things environment and advantageously being configured to cooperate
[0292] 5 with other robots or computers.
[0293]
[0187] According to an embodiment, the sender device SEND 20 can be an artificial intelligence configured to cooperate with robots and / or computers and / or other artificial intelligences.
[0294]
[0188] According to an embodiment, the sender device SEND 20 can comprise at least one processor, and preferably at least one non-volatile memory. Said processor is advantageously configured to
[0295] 10 execute the steps executed by the sender device SEND 20.
[0296]
[0189] According to an embodiment, the receiver device REC 30 can be an electronic device comprising a user interface. Said user interface being configured to allow a user to evaluate the result of a voting session, for example.
[0297]
[0190] According to an embodiment, the receiver device REC 30 can be a robot, preferably said robot
[0298] 15 being part of an Internet of Things environment and advantageously being configured to cooperate with other robots or computers.
[0299]
[0191] According to an embodiment, the receiver device REC 30 can be an artificial intelligence configured to cooperate with robots and / or computers and / or other artificial intelligences.
[0300]
[0192] According to an embodiment, the receiver device REC 30 can comprise at least one processor,
[0301] 20 and preferably at least one non-volatile memory. Said processor is advantageously configured to execute the steps executed by the receiver device REC 30.
[0302]
[0193] According to an embodiment, the present invention can be used in a electronic environment, for example in a non-secured electronic environment, wherein a vote can be needed regarding at least one action to be taken. For example, the present invention can be used to allow artificial
[0303] 25 intelligences to vote regarding a decision to be taken. For example, as illustrated by figure 4, the system according to the present invention can comprise a plurality of sender devices SEND 20a to 20g, such as a plurality of artificial intelligences, and regarding a decision to be taken, a vote can be organized. Each artificial intelligence 20a to 20g will therefore produce a vote using the present invention.
[0304] 30
[0194] In the present description, one module can comprise several modules, one module can be formed of several modules.
[0305]
[0195] According to an embodiment, the present invention can be configured to cooperate with at least one input module including one or more user interface devices such as a keyboard, pointer, number pad, or touch screen.
[0306] 35
[0196] In the present description, a processor may be any logic processing unit, such as one or more digital processors, microprocessors, central processing units, graphics processing units, application-specific integrated circuits, programmable gate arrays, programmed logic units, digital signal processors, network processors, and the like.
[0307]
[0197] In the present description, a storage device or module is at least one non-transitory or tangible
[0308] 40 storage device or module. A storage module can, for example, include one or more volatile storage devices, for instance random access memory, and one or more non-volatile storage devices, for instance read only memory, flash memory, magnetic hard disk, optical disk, solid state disk, and the like.
[0309]
[0198] In the present description, a storage module can include or store processor-executable instructions
[0310] 45 and / or processor-readable data associated with the operation of the present invention and / or with the execution of the method of the present invention. Execution of processor-executable instructions and / or data causes the at least one processor, and / or control modules or units, to carry out various processes and actions.
[0311]
[0199] Unless otherwise specified herein, or unless the context clearly dictates otherwise the term about
[0312] 50 modifying a numerical quantity means plus or minus ten percent. Unless otherwise specified, or
[0313] 31 unless the context dictates otherwise, between two numerical values is to be read as between and including the two numerical values.
[0314]
[0200] In the present description, some specific details are included to provide an understanding of various disclosed implementations. The skilled person in the relevant art, however, will recognize that
[0315] 5 implementations may be practiced without one or more of these specific details, parts of a method, components, materials, etc.
[0316]
[0201] In the present description and appended claims "a", "an", "one", or "another" applied to "embodiment", "example", or "implementation" is used in the sense that a particular referent feature, structure, or characteristic described in connection with the embodiment, example, or
[0317] 10 implementation is included in at least one embodiment, example, or implementation. Thus, phrases like "in one embodiment", "in an embodiment", or "another embodiment" are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments, examples, or implementations.
[0318] 15
[0202] As used in this description and the appended claims, the singular forms of articles, such as "a", "an", and "the", can include plural referents unless the context mandates otherwise. Unless the context requires otherwise, throughout this description and appended claims, the word "comprise" and variations thereof, such as, "comprises" and "comprising" are to be interpreted in an open, inclusive sense, that is, as "including, but not limited to".
[0319] 20
[0203] All publications referred to in this description, are incorporated by reference in their entireties for all purposes herein.
[0320]
[0204] While certain features of the described embodiments and implementations have been described herein, many modifications, substitutions, changes and equivalents will now occur to the skilled person in the relevant art. It is, therefore, to be understood that the appended claims are intended
[0321] 25 to cover all such modifications and changes as fall within the scope of the described embodiments and implementations.
[0322]
[0205] References:
[0323] 10 Authority device
[0324] 11 Initialization module IM
[0325] 30 20 Sender device SEND
[0326] 20a . 20g Artificial intelligences
[0327] 21 Encryption module EM
[0328] 22 First proof module PM1
[0329] 23 First randomization module RM1
[0330] 35 24 First computational module CM1
[0331] 25 Generation module GM
[0332] 26 Sending module SM
[0333] 30 Receiver device REC
[0334] 31 Verification module
[0335] 40 32 Second randomization module RM2
[0336] 33 Second computational module CM2
[0337] 34 Second proof module PM2
[0338] 35 Storing module STM
[0339] 100 Method
[0340] 32 101 Initialization step
[0341] 102 Ciphertext creation step
[0342] 103 Proof creation step
[0343] 104 Generation step
[0344] 5 105 Sending step
[0345] 106 Verification step
[0346] 107 Second randomization step
[0347] 108 Second computation step
[0348] 109 Third computation step
[0349] 10 110 Second proof creation step
[0350] 111 Storing step
[0351] 33
Claims
Claims1. A linearly homomorphic signature method (100) for zero-knowledge proofs of subset membership on at least one EIGamal ciphertext in a group with a generator P of prime order p regarding at least one subsetof N authorized plaintexts, said plaintexts being authorized5 by at least one authority device AUT (10), said cyphertext being generated from a plaintext taken among said subsetsaid method being executable by at least one computing system, preferably said computing system being communicatively connected to at least one communication network, said method (100) using randomizable tags, said method (100) comprising at least: o An initialization step (101), preferably executed by said authority device AUT (10) using at10 least one initialization module IM (11), said initialization step (101) comprising at least a generation step of at least:• one pair of EIGamal encryption keys (DK, EK) for plaintexts comprised by a groupwherein the decryption key DK is generated asand the encryption key EK is generated aswherein z is private vector15 of scalars and P is said generator of the group G of prime order p\• one pair of linearly homomorphic signature keys (SK, VK) for messages insaid messages comprising at least ciphertexts;• N verifiable tags• N pairs of signatures such as:20Wherein is configured to characterize a proof on the subset preferably,whereis a full-domain hash function into;Said initialization step (101) generating a set of public parameters comprising:25o A ciphertext creation step (102) with proof of subset membership, preferably executed by at least one sender device SEND (20) using at least one encryption module EM (21), said ciphertext creation step (102) comprising the generation of at least one EIGamal ciphertext for at least one authorized plaintext for a given j, with a random30 scalarsuch as:o A proof creation step (103), preferably executed by at least said sender device SEND (20) using at least a first proof module PM1 (22), of at least said proof from andcomprising:34• a first randomization step, preferably executed by said sender device SEND (20) using at least a first randomization module RM1 (23), said first randomization step comprising a randomization of at least oneintofor said given j;• a first computation step, preferably executed by said sender device SEND (20)5 using at least a first computational module CM1 (24), ofwherein:is a valid signature ofunder VK for the tagis a valid signature of a randomizerunder VK for the tago A generation step (104), preferably executed by said sender device SEND (20) using at least a generation module GM (25), comprising at least:10 • Generating a pair of linearly homomorphic signing-verification keys (sk,vk) for messages in• Generating signaturesandwherein:15 o A sending step (105), preferably executed by said sender device SEND (20) using at least a sending module SM (26), from the sender device SEND (20) to at least one receiver device REC (30) of the ciphertextsandtogether with the proofcomprisingand with the signatureso A verification step (106), preferably executed by said receiver device REC (30) using at20 least one verification module VM (31), said verification step comprising at least the verification of at least:• the validity of Tag';• the validity of the signature( ) under VK for the tag Tag', and the validity of the signatureunder VK for the tag Tag';25 • the validity of the signaturesonunder vk andonunder vk. o A second randomization step (107), preferably executed by said receiver device REC (30) using at least a second randomization module RM2 (32), of said EIGamal ciphertext( ) to generate the ciphertextusing a random scalarand a randomizer30such as:o A second computation step (108), preferably executed by said receiver device REC (30) using at least a second computational module CM2 (33), of a signature35being a valid signature ofunder VK for the tag Tag';35o A third computation step (109), preferably executed by said receiver device REC (30) using at least said computational module CM2 (33), of a signaturewherein is a valid signature ofunder vk;5 o A second proof creation step (110), preferably executed by at least said receiver device REC (30) using at least a second proof module PR2 (34), of a proof from said prooffrom Tag' andcomprising:• A third randomization step by at least said second randomization module RM2 (32) of the tag Tag' into Tag" ;10 • A fourth computation step by at least said second computational module CM2 (33) of the signaturebeing a valid signature ofunder VK for the tag Tag"; o A storing step (111), preferably executed by the receiver device REC (30) using at least a storing module STM (35), of the ciphertexttogether with said proof15 comprisingand with the signaturewhich are configured to be publicly verified and wherein:• Tag" is a valid tag;•is a valid signature onunder VK for the tag Tag" allowing to prove that the plaintext is in the subset20 •is a valid signature onunder vk.
2. The method (100) according to the previous claim wherein, in a bilinear setting( ) the pair of linearly homomorphic signing-verification keys (sk,vk) for messages inare generated such as:25 and,30 3. The method (100) according to the previous claim wherein: o four random pointsare generated and appended to the public parameters, for the Groth-Sahai proofs; o the proof, fromand is generated such as:36whereinis a V3lid signature ofunder VK for the tagand whereinis a valid signature of under VK for the tago the generation step comprises generating a Diffie-Hellman value W = r • H, for H -and generating a Groth-Sahai proofof Diffie-Hellman tuple for (P, C0,H, W).5 o the sending step from the sender device SEND (20) to the receiver device REC (30) comprises the sending of the value W and of the proof o the verification step comprises the verification of the validity of the Diffie-Hellman proof on the tuple o10o the randomization of said EIGamal ciphertextto generate the ciphertextusing a random scalais such as:o the second computation step comprises a computation of the randomized Groth-Sahai15 proofbeing a valid Diffie-Hellman proof on the tupleg o the storing step comprises the storing of4. The method (100) according to claim 1 wherein, in a bilinear settingo four random points, , are generated, and appended to the public20 parameters, for the Groth-Sahai proofs; o the pair of linearly homomorphic signing-verification keys SK and VK are generated such aso the N verifiable tags Tagy are generated such aswith their validity proofs25 o the N pairs of signatures, forare generated such as:oare defined as:30with a random scalaro the proof is generated, from such as:37o One authority device AUT (10) comprising at least one initialization module IM (11), said initialization module IM (11) being configured to execute said initialization step (101). o One sender device SEND (20) comprising at least:• An encryption module EM (21) being configured to execute said ciphertext creation5 step (102).• A first proof module PM1 (22) being configured to execute said proof creation step (103). Said first proof module PM1 (22) comprising at least:■ A first randomization module RM1 (23) being configured to execute said first randomization step;10 ■ A first computational module CM1 (24) being configured to execute said first computation step.• A generation module GM (25) being configured to execute said generation step (104);• A sending module SM (26) being configured to execute the sending step (105),15 and advantageously to communicate with at least one receiver device REC (30). o One receiver device REC (30) comprising at least:• A verification module VM (31) being configured to execute said verification step (106);• A second randomization module RM2 (32) being configured to execute said20 second randomization step (107), and the third randomization step;• A second computational module CM2 (33) being configured to execute said second computational step (108), said third computational step (109) and said fourth randomization step;• A second proof module PM2 (34) being configured to execute said second proof25 creation step (110);• A storing module STM (35) being configured to execute said storing step (111).
10. The voting system according to claim 9 wherein at least one among the authority device AUT (10), the sender device SEND (20) and the receiver device REC (30) is taken among: a robot, a30 smartphone, an Internet of Thing device, an artificial intelligence, a computer.41
Citation Information
Cited By
Quantum computing attack resistant traceable receipt-free encryption method and system
CN122372347A
