Changes between Version 68 and Version 69 of Crypto/CurrentSpecs


Ignore:
Timestamp:
Feb 13, 2013 3:22:05 PM (6 years ago)
Author:
zzz
Comment:

add sud key revocation info

Legend:

Unmodified
Added
Removed
Modified
  • Crypto/CurrentSpecs

    v68 v69  
    4646|| Datagram signing || DSA || Years and years? || || Or is it the other LS key?  There's multiple keys in a LS, some are in the Dest (i.e. tied to the hosts.txt entry) and some are regenerated at startup. Of course for client tunnels, keys are not persistent, all are regenerated at startup (or on reconnect if so configured in i2ptunnel) ||
    4747|| Streaming message signing || DSA || Years and years? || || ditto ||
    48 || SUD signing || DSA || Years and years || 99% verif. || New file format required to change algo, proposal at http://zzz.i2p/topics/1351  ||
     48|| SUD signing || DSA || Years and years || 99% verif. || Keys are hardcoded in i2p source, and revokable by removing them. New file format required to change algo, proposal at http://zzz.i2p/topics/1351  ||
    4949|| Tunnel Build Messages [8] || ElG ||  ||  || ||
    5050|| NetDB Lookups / Stores [8] || ElG/AES+SessionTag || Years but... ||  || Only some are encrypted [8] Right now there's no limit on RI key lifetime but we could force a regeneration after a certain amount of time ||