RusstopiaLabs
/
xs
mirror of https://gogs.blitter.com/RLabs/xs
1
0
Fork 0
Code Issues Releases Wiki Activity

Update 'README.md' 

Rewording note on algo remodulation
This commit is contained in:
Russtopia 2023-11-30 21:23:03 -08:00
parent e6a2b7f2cd
commit 25fc7b157a
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -70,7 +70,8 @@ Support has been added for an experimental 'remodulation' of the active session
when a rekey is performed. This feature, only active if the `-R` option is specified by *both* server and
client, will cause the two sides to negotiate a (potentially) new cipher and hash algorithm as part of the rekeying (normal rekeying *without* 'remodulation' is on by default, with the interval optionally specified independently by client and server via the `-r` (note lowercase) option).
This experimental 'remodulation' is intended to further confuse a potential attacker attempting to analyze session data; however if the initial session key negotiation, protected by the asymmetric KEM exchange, were broken AND the attacker has recorded all following session data, the attacker could in theory stay in sync with rekeys *and* algo remodulations in order to continue decrypting session data, so NOTE that this protection is still predicated on the security of the initial asymmetric KEM exchange.
This experimental 'remodulation' is intended to inhibit a potential attacker's efforts to analyze session data, by reducing the usefulness of any distinguisher, presuming one exists, that may exist in one of the symmetric cipher algos used during a session. Note however, that if the initial KEM negotiation were broken and the attacker has recorded all following session traffic, they can still 'stay in sync' with the rekeys *and* algo remodulations, and be able to continue decrypting across session rekeys. (That is, this feature does not
add any security if the initial KEM exchange were broken.)
***
### Conn