... | ... | @@ -20,10 +20,12 @@ The messages exchanged between two contacts referring to a given private group c |
|
|
|
|
|
The protocol uses four message types.
|
|
|
|
|
|
**0: INVITE** - Sent by the creator to the invitee. The message body is a BDF list with six elements: `messageType` (int), `creator` (list), `groupName` (string), `salt` (raw), `message` (string or null), and `signature` (raw).
|
|
|
**0: INVITE** - Sent by the creator to the invitee. The message body is a BDF list with six elements: `messageType` (int), `creator` (list), `groupName` (string), `salt` (raw), `text` (string or null), and `signature` (raw).
|
|
|
|
|
|
`creator`, `groupName` and `salt` are taken from the private group descriptor. `creator` must be the identity of the contact who sent the message.
|
|
|
|
|
|
`text` is an optional message from the creator to the invitee explaining the invitation.
|
|
|
|
|
|
The signature covers a BDF list with three elements: `timestamp` (int), `contactGroupId` (unique ID), and `privateGroupId` (unique ID). The timestamp and contact group ID are taken from the message header. The private group ID is calculated from the private group descriptor. The public key from the private group descriptor is used to validate the signature. The signature label is `org.briarproject.briar.privategroup.invitation/INVITE`.
|
|
|
|
|
|
The creator sets the private group's visibility to VISIBLE when sending an invite message.
|
... | ... | |