status-im
/
specs
mirror of https://github.com/status-im/specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix envelope encryption vs signing for P2P request

This commit is contained in:
kdeme 2019-12-11 10:55:30 +01:00
parent 9e3d62e1c9
commit f550b6bab0
No known key found for this signature in database
GPG Key ID: 4E8DD21420AF43F5
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
status-whisper-mailserver-spec.md
View File

@ -51,7 +51,7 @@ In the Whisper envelope's payload section, there MUST be RLP-encoded information
The `Cursor` field SHOULD be filled in if a number of envelopes between `Lower` and `Upper` is greater than `Limit` so that the requester can send another request using the obtained `Cursor` value. What exactly is in the `Cursor` is up to the implementation. The requester SHOULD NOT use a `Cursor` obtained from one mailserver in a request to another mailserver because the format or the result MAY be different. The `Cursor` field SHOULD be filled in if a number of envelopes between `Lower` and `Upper` is greater than `Limit` so that the requester can send another request using the obtained `Cursor` value. What exactly is in the `Cursor` is up to the implementation. The requester SHOULD NOT use a `Cursor` obtained from one mailserver in a request to another mailserver because the format or the result MAY be different.
The envelope MUST be signed with a symmetric key agreed between the requester and Mailserver. The envelope MUST be encrypted with a symmetric key agreed between the requester and Mailserver.
### Receiving historic messages ### Receiving historic messages