I2P Website issueshttps://i2pgit.org/i2p-hackers/i2p.www/-/issues2023-04-28T19:04:42Zhttps://i2pgit.org/i2p-hackers/i2p.www/-/issues/10Document why signature in SSU SessionCreated msg is encrypted2023-04-28T19:04:42ZidkDocument why signature in SSU SessionCreated msg is encryptedOpened [5 years ago](/timeline?from=2016-09-16T17%3A56%3A28Z&precision=second "See timeline at Sep 16, 2016 5:56:28 PM")
Last modified [5 years ago](/timeline?from=2016-09-17T18%3A10%3A28Z&precision=second "See timeline at Sep 17, 2016 ...Opened [5 years ago](/timeline?from=2016-09-16T17%3A56%3A28Z&precision=second "See timeline at Sep 16, 2016 5:56:28 PM")
Last modified [5 years ago](/timeline?from=2016-09-17T18%3A10%3A28Z&precision=second "See timeline at Sep 17, 2016 6:10:28 PM")
## [\#1849](/ticket/1849)[new](/query?status=new)[enhancement](/query?status=!closed&type=enhancement)
# Document why signature in SSU SessionCreated msg is encrypted
Reported by:[zzz](/query?status=!closed&reporter=zzz)Owned by:
Priority:
[minor](/query?status=!closed&priority=minor)
Milestone:
[eventually](/milestone/eventually "No date set")
Component:
[www/i2p](/query?status=!closed&component=www%2Fi2p)
Version:
[0.9.26](/query?status=!closed&version=0.9.26)
Keywords:
Cc:
Parent Tickets:
Sensitive:
[no](/query?status=!closed&sensitive=0)
### 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.
<EinMByte> zzz: Ah, I found out why we need to encrypt the signature
<EinMByte> or at least why we do it
<EinMByte> zzz: An attacker could substitute the signature with their own signature, and hence claim to have sent the message
<EinMByte> 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
<EinMByte> But maybe it's a good idea to keep the encryption there anyway, just in case that is probably
<EinMByte> For sure, there MUST be a note on there
<EinMByte> s/there/that
### Subticketseventuallyhttps://i2pgit.org/i2p-hackers/i2p.www/-/issues/9Document all options2021-04-30T03:53:37ZidkDocument all optionsOpened [6 years ago](/timeline?from=2015-10-12T13%3A52%3A35Z&precision=second "See timeline at Oct 12, 2015 1:52:35 PM")
Last modified [3 years ago](/timeline?from=2018-06-19T16%3A40%3A33Z&precision=second "See timeline at Jun 19, 2018 ...Opened [6 years ago](/timeline?from=2015-10-12T13%3A52%3A35Z&precision=second "See timeline at Oct 12, 2015 1:52:35 PM")
Last modified [3 years ago](/timeline?from=2018-06-19T16%3A40%3A33Z&precision=second "See timeline at Jun 19, 2018 4:40:33 PM")
## [\#1677](/ticket/1677)[assigned](/query?status=assigned)[task](/query?status=!closed&type=task)
# Document all options
Reported by:[zzz](/query?status=!closed&reporter=zzz)Owned by:[sadie](/query?status=!closed&owner=sadie)
Priority:
[minor](/query?status=!closed&priority=minor)
Milestone:
[eventually](/milestone/eventually "No date set")
Component:
[www/i2p](/query?status=!closed&component=www%2Fi2p)
Version:
[0.9.22](/query?status=!closed&version=0.9.22)
Keywords:
[docs](/query?status=!closed&keywords=~docs)
Cc:
[slumlord](/query?status=!closed&cc=~slumlord)
Parent Tickets:
Sensitive:
[no](/query?status=!closed&sensitive=0)
### Description
Perennial request
Some attempts and proposals:
- [http://echelon.i2p/docs/advanced.options.txt](http://echelon.i2p/docs/advanced.options.txt)
- Similar effort for rate stats: [http://i2p-projekt.i2p/en/misc/ratestats](http://i2p-projekt.i2p/en/misc/ratestats)
- str4d proposed extending Properties and our utils to preserve comment lines when reading/saving, sounds hard
- We could pull them out of the javadocs somehow
My theory was always that you don't need a list, you should just find the docs for what you want to do, but everybody loves a list.
However we format the results, first we need the descriptions for each.
See below for my list.
### Subticketseventually