Closed ghost closed 10 years ago
But how do we know which public key we have to use to check the signature?
Edit: Thus it cannot verify the "integrity" before decrypting the AES key and decrypting the actual message (which eventually contains the sender id).
I wrote a possible illustration of the transport message format. https://github.com/Qabel/intern-doc/wiki/Qabel-Client-Drop#transport-format I know the table is ugly. It's the best I could think of in markdown...
The header is currently just a proposal. We have to discuss this on monday.
On 8. August 2014 16:20:15 MESZ, Christian Burkert notifications@github.com wrote:
I wrote a possible illustration of the transport message format. https://github.com/Qabel/intern-doc/wiki/Qabel-Client-Drop#transport-format I know the table is ugly. It's the best I could think of in markdown...
Reply to this email directly or view it on GitHub: https://github.com/Qabel/intern-doc/issues/9#issuecomment-51608088
Encrypt ciphertext: Pro:
Con:
Encrypt plaintext: Pro:
Cons:
We currently tend to sign the ciphertext. But changes might occur after further discussion.
Hi @Gottox and @thechauffeur! And also the rest!
Can you review this document. Is that a solution we can live with it https://github.com/Qabel/intern-doc/wiki/Qabel-Client-Drop
CU k-c13