Document why signature in SSU SessionCreated msg is encrypted
Opened 5 years ago
Last modified 5 years ago
#1849newenhancement
Document why signature in SSU SessionCreated msg is encrypted
Reported by:zzzOwned by: Priority: minor Milestone: eventually Component: www/i2p Version: 0.9.26 Keywords:
Cc:
Parent Tickets:
Sensitive: no
Description
Add to the SSU overview and/or spec.
Also research in java code, mtn commits, and 10-year-old meeting logs, status notes, and emails for additional info.
zzz: Ah, I found out why we need to encrypt the signature
or at least why we do it
zzz: An attacker could substitute the signature with their own signature, and hence claim to have sent the message
zzz: But it does not seems to be applicable to I2P, because both parties know each others RI and hence public keys
EinMByte> zzz: It all comes down to whether or not it is feasible for an attacker to intercept the DatabaseStoreMessage?, and substitute it with their own
But maybe it's a good idea to keep the encryption there anyway, just in case that is probably
For sure, there MUST be a note on there
s/there/that