Opened 10 months ago

Closed 7 months ago

#22722 closed defect (fixed)

tor-spec still says "For a public-key cipher, we use RSA with 1024-bit keys"

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.3.2.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-spec, spec
Cc: Actual Points:
Parent ID: Points: 0.5
Reviewer: Sponsor:


In 0.3. Ciphers, tor-spec.txt says we use 1024-bit rsa as our public key cipher.

Later, it turns out we use other things, but if you're just reading from the top, you will conclude that we're still relying on 1024-bit rsa for everything (which would be bad).

We should update the 0.3. Ciphers section to include the ciphers we use now. Or we should rework things so there doesn't need to be a 0.3. Ciphers section that apparently doesn't get updated when the other parts of the spec get updated. :)

Child Tickets

Change History (4)

comment:1 Changed 10 months ago by catalyst

Milestone: Tor: 0.3.2.x-final
Points: 0.5

comment:2 Changed 10 months ago by arma

Keywords: tor-spec added; torspec removed

switch to tor-spec keyword like most tickets seem to use

comment:3 Changed 7 months ago by nickm

Keywords: spec added

Add 'spec' keyword to items that are just spec fixes. These can land after the feature-freeze.

comment:4 Changed 7 months ago by nickm

Resolution: fixed
Status: newclosed

I took a mostly local approach in 0.3 in 51f1127c2fea9b34ee32bbf8b56ea2658424b9f2.

I think we should at some point do a more thorough rewrite of the spec, but at least 0.3 is not currently misleading.

Note: See TracTickets for help on using tickets.