You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that we are using ECIES now and moved away from RSA.
Does
/** * public key in PEM encoding format */
string publicEncryptionKey=1;/** * A number used to later identify the publicEncryptionKey. * When a message is sent to the creator of this contact, and it is encrypted * with the publicEncryptionKey, this identifier is also sent, so the recipient * knows which key to use to decrypt it. If the recipient creates multiple * keys for multiple pairings, then they should remember the publicKeyId that * they chose for each one, so they won't have to try all the keys during decryption. */int32publicKeyId=2;
Still make sense keeping?
AFAIK, encryption will be through a symmetric secret generated by an agreement (ECDH) after public key exchange.
We should only need the publicKeys of the other parties to perform both encryption and signature verification?
The text was updated successfully, but these errors were encountered:
Given that we are using ECIES now and moved away from RSA.
Does
Still make sense keeping?
AFAIK, encryption will be through a symmetric secret generated by an agreement (ECDH) after public key exchange.
We should only need the publicKeys of the other parties to perform both encryption and signature verification?
The text was updated successfully, but these errors were encountered: