## 1. Introduction

This is a brief article that introduces the concept of a ring signature. In parts 4, 5, 6, and 7 we will look at specific instances of ring signature schemes — including those used in earlier and more recent versions of the Monero project — and analyze their security properties.

In 1991, Chaum and Van Heyst introduced a new class of signature schemes known as *group signatures*[2]. The core of the model consisted of a trusted entity known as the *group manager* that clusters a subset of users together into a group. The group manager provides each member of the group with a separate private key. The ingenuity of this structure lies in the fact that any member can sign messages in an anonymous fashion. This means that anybody who can access the signature, can also verify that it was created by one of the group members without knowing who specifically. The only entity that can identify the real signer is the trusted group manager. In group signature schemes, the anonymity of signers comes at the expense of relinquishing power to the group manager. Indeed, the trusted group manager is the only entity that:

- Decides who joins the group.
- Decides which member(s) get(s) banned from the group.
- Chooses the private key allocated to each member of the group.
- Identifies the real signer whenever a message is signed.

This setting works best if the group members agreed to cooperate beforehand . The group manager can then serve as the enforcer of this cooperation, revoking the membership of anyone trying to game the system.

The *anonymity* of group signatures paved the way to another class of *signer-ambiguous* shemes known as *ring signature *schemes. The expression *ring signature* was first coined by Rivest, Shamir, and Tauman[3]. Note that schemes fitting the definition of a ring signature have been proposed way before the publication of this paper. In a ring signature, there does not exist a pre-defined group of users. As a consequence, there does not exist any omnipotent group manager. Instead, the actual signer defines a set of members of her choosing before she signs a message. This set is known as a *ring*. The only constraint is that the ring must include the actual signer. The signer creates a signature using her private key and all the other ring members’ public keys. The ring can be arbitrary without the need to inform selected members of their participation — (all that is needed is access to their public keys which is usually common knowledge). The reason behind adopting the *ring* terminology is that *“rings are geometric regions with uniform periphery and no center”*[3].

## 2. Ring Signature Definition and Security analysis

A ring signature on a message is a string that depends on:

- The message .
- The public and secret keys of the signer.
- The public keys associated with an arbitrarily-specified ring of users.
- Some randomly chosen data.

Anyone can check whether it corresponds to a member of the ring but can not know the identity of the actual signer. More formaly, a generic digital signature scheme is defined as a set of 3 algorithms:

**The key generation algorithm**. On input , where is the security parameter, it produces a pair of matching public and secret keys. The algorithm is modeled as a PPT Turing machine.**The ring signing algorithm**. Suppose a user decides to sign a message on behalf of a ring of users . takes three inputs including:- The message .
- The set of the public keys of the ring members
- The private key of the signer .

It then outputs a ring signature on message . The algorithm is modeled as a PPT Turing machine.

**The ring verification algorithm**. Given a ring siganture , a message , the set of public keys of the ring members, is a boolean function that returns if the signature is valid and otherwise. is a deterministic algorithm as opposed to probabilistic.

When we introduced digital signature schemes with only one user (part 1 of this series), we mandated two security measures:

**Correctness**: Any signature generated by must pass the verification test with overwhelming probability.**EFACM Unforgeability**: Even when an adversary can have access to valid signatures on any messages of his choosing — other than –, the probability that he successfully forges a signature on message must be negligible in .

For a ring signature, the EFACM mechanics differ slightly from the non-ring case described in previous parts. [1] defines various models for existential forgeability. The one we use in this work is known as *unforgeability against fixed-ring attacks*. It is defined as follows in [1]:

- , key pairs are generated using , and the ring is fed to the adversary.
- The adversary can access any ROs applicable in the scheme, and can also access a signing oracle:
Range of signatures.
takes an index and a message , and outputs a signature authored by ring member on message . In other terms,

- The adversary outputs a valid forgery (i.e., one that passes ‘s test). Moreover, the adversary must have never queried on message .

In a *fixed-ring attack*, the adversary can only query the signing oracle on the full ring . That means that signatures issued by the signing oracle are created with respect to . Moreover, ‘s verification algorithm is conducted with respect to .

For a ring signature, we add a third security requirement: *Anonymity*. In what follows, we introduce two definitions of anonymity also known as signer-ambiguity. The distinction between the two definitions has to do with the possibility that in a set of ring members, a subset of them may be compromised (i.e., their private keys may be stolen or known).

**Anonymity definition #1**: Given any subset , , of compromised members of a ring with elements, an adversary can not do better than random guessing over all elements when trying to identify the real signer. This definition may seem counter-intuitive: if we know the private key of a member, we would think that we should be able to say whether she is the actual signer or not. However, this definition states that even if the private keys of all the members are revealed, no adversary can identify the real signer with probability better than random guessing over all members. More formally, let be a PPT adversary with random tape that takes 4 inputs:- Any message .
- A ring of the public keys of the ring members. includes the public key of the actual signer.
- A list of compromised private keys of ring members (). Note that can be empty. Also note that may be different than but we always have
- A valid signature on message , with ring and actual signer private key .

outputs an index corresponding to the ring member in that it thinks is the actual signer.

This definition of signer-ambiguity mandates that for any polynomial in the security parameter we have:

Roughly speaking, that means that the probability of guessing the real signer is . The definition implies the

*exculpability*of any user. This means that even if a signer is coerced or subpoenaed to release her private key, nothing can be done to prove that she is the real signer.**Anonymity definition #2**: This definition is a bit weaker than the first one in the sense that if the adversary knows secret keys out (excluding that of the signer), the best he can do is randomly guess over the remaining uncompromised members. In this definition, having access to a secret key can either help confirm or rule out whether the corresponding ring member is the actual signer. Contrary to definition #1, this definition does not ensure exculpability as previously defined. More formally, and using the same notation introduced earlier, definition #2 mandates that:ifif

## References

[1] A. Bender, J. Katz, and R. Morselli. Ring signatures: Stronger denitions, and constructions without random oracles. Journal of Cryptology, 22(1):114-138, 2008.

[2] D. Chaum and E. Van Heyst. Group signatures. Advances in Cryptology – EUROCRYPT ’91, Lecture Notes in Computer science(547):257-265, 1991.

[3] R. Rivest, A. Shamir, and Y. Tauman. How to leak a secret. Advances in Cryptology – Asiacrypt 2001, Lecture Notes in Computer Science(2248):552-565, 2004.

**Tags:** anonymity, group signature, Monero, Privacy, ring signature

## No comments

Comments feed for this article

Trackback link: https://delfr.com/moneros-part-3-10-ring-signatures/trackback/