Forum signature must cover the timestamp

akwizgran
2015-04-24 16:04:16 +00:00
parent cbdd21a423
commit 9bea3ac07d

@@ -22,7 +22,7 @@ The client identifer is random:
If `author` is null, the post is anonymous and `signature` must also be null. Otherwise `author` is a list with two elements: `name` (string) and `public_key` (raw).
If `signature` is null, the post is anonymous and `author` must also be null. Otherwise `signature` is a signature with `public_key` calculated over a list with four elements: `forum`, `author`, `content` and `timestamp` (int). `forum`, `author` and `content` are described above. `timestamp` is the timestamp from the [message header](BSP#message-format).
If `signature` is null, the post is anonymous and `author` must also be null. Otherwise `signature` is a signature with `public_key`, calculated over a list with four elements: `forum`, `author`, `content` and `timestamp` (int). `forum`, `author` and `content` are described above. `timestamp` is the timestamp from the [message header](BSP#message-format).
**4: ATTACHMENT** - The content is raw data.
@@ -33,7 +33,7 @@ If `signature` is null, the post is anonymous and `author` must also be null. Ot
* An invitation is valid if it is well-formed.
* A response is valid if it is well-formed and it references a valid invitation created by the opposite peer.
* A departure is valid if it is well-formed and it references a valid invitation created by either peer.
* A post is valid if it is well-formed, its parent (if any) is a valid post, and it is either anonymous or carries a valid signature over its content.
* A post is valid if it is well-formed, its parent (if any) is a valid post, and it is either anonymous or carries a valid signature.
* An attachment is always valid.
Note that a post can be validated before its attachments have been received, and an attachment can be validated before it has been completely received.