Group signature

A group signature scheme is a method for allowing a member of a group to anonymously sign a message on behalf of the group. The concept was first introduced by David Chaum and Eugene van Heyst in 1991. For example, a group signature scheme could be used by an employee of a large company where it is sufficient for a verifier to know a message was signed by an employee, but not which particular employee signed it. Another application is for keycard access to restricted areas where it is inappropriate to track individual employee's movements, but necessary to secure areas to only employees in the group.

Essential to a group signature scheme is a group manager, who is in charge of adding group members and has the ability to reveal the original signer in the event of disputes. In some systems the responsibilities of adding members and revoking signature anonymity are separated and given to a membership manager and revocation manager respectively. Many schemes have been proposed, however all should follow these basic requirements:

Soundness and completeness
Valid signatures by group members always verify correctly, and invalid signatures always fail verification.
Unforgeable
Only members of the group can create valid group signatures.
Anonymity
Given a message and its signature, the identity of the individual signer cannot be determined without the group manager's secret key.
Traceability
Given any valid signature, the group manager should be able to trace which user issued the signature. (This and the previous requirement imply that only the group manager can break users' anonymity.)
Unlinkability
Given two messages and their signatures, we cannot tell if the signatures were from the same signer or not.
No framing
Even if all other group members (and the managers) collude, they cannot forge a signature for a non-participating group member.
Unforgeable tracing verification
The revocation manager cannot falsely accuse a signer of creating a signature he did not create.
Coalition resistance
A colluding subset of group members cannot generate a valid signature that the group manager cannot link to one of the colluding group members.[1]

The ACJT 2000,[1] BBS04,[2] and BS04 (in CCS) group signature schemes are some of the state of the art. (Note: this might be an incomplete list.)

Boneh, Boyen and Shacham published in 2004 (BBS04, Crypto04) a novel group signature scheme based on bilinear maps.[2] Signatures in this scheme are approximately the size of a standard RSA signature (around 200 bytes). The security of the scheme is proven in the random oracle model and relies on the Strong Diffie Hellman assumption (SDH) and a new assumption in bilinear groups called the Decision linear assumption (DLin).

A more formal definition that is geared towards provable security was given by Bellare, Micciancio and Warinschi.[3]

  1. ^ a b Ateniese, Giuseppe; Camenisch, Jan; Joye, Marc; Tsudik, Gene (2000). "A Practical and Provably Secure Coalition-Resistant Group Signature Scheme". Advances in Cryptology — CRYPTO 2000 (PDF). Lecture Notes in Computer Science. Vol. 1880. pp. 225–270. doi:10.1007/3-540-44598-6_16. ISBN 978-3-540-67907-3. Retrieved 24 June 2012.
  2. ^ a b Boneh, Dan; Boyen, Xavier; Shacham, Hovav (2004). "Short Group Signatures" (PDF). Advances in Cryptology – CRYPTO 2004. Lecture Notes in Computer Science. Vol. 3152. Springer. pp. 227–242. doi:10.1007/978-3-540-28628-8_3. ISBN 978-3-540-22668-0. ISSN 0302-9743. Retrieved 24 June 2012.
  3. ^ Bellare, Mihir; Micciancio, Daniele; Warinschi, Bogdan (May 2003). "Foundations of Group Signatures: Formal Definitions, Simplified Requirements, and a Construction Based on General Assumptions". Advances in Cryptology — EUROCRYPT 2003. Lecture Notes in Computer Science. Vol. 2656. Warsaw, Poland: Springer. pp. 614–629. doi:10.1007/3-540-39200-9_38. ISBN 978-3-540-14039-9.