Opened 4 years ago

Closed 2 years ago

#16680 closed defect (wontfix)

make Ed25519 master key, signing key and cert ascii-armored on disk by default

Reported by: s7r Owned by: nickm
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7.2-alpha
Severity: Normal Keywords: ed25519, keys, ascii-armored
Cc: asn, nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

As discussed in #16645: (Ed25519 key backups) printing it on paper, QR codes, email, cloud, portable storage media, backup servers, you name it should all be possible for an user.

I suggest using Base58Check encoding (it removes 0OIl chars) - makes it easier to re-create the key from a paper printed version of it.

An ascii-armored version for the key files should be used by default regardless if the master Ed25519 key is encrypted with a passphrase or not.

Child Tickets

Change History (11)

comment:1 Changed 4 years ago by nickm

Priority: normalminor

I don't mind this idea, but I need to give it a lower priority while I'm working on all the other ed25519 stuff. :)

comment:2 Changed 4 years ago by nickm

Keywords: TorCoreTeam201508 added
Owner: set to nickm
Status: newassigned

comment:3 Changed 4 years ago by nickm

On reflection I think we should can this to 0.2.8 or later. Any objections?

comment:4 Changed 4 years ago by nickm

Keywords: TorCoreTeam201508 removed
Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:5 Changed 4 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

comment:6 Changed 4 years ago by ohheyalan@…

Severity: Normal

I think this is a great idea!

comment:7 Changed 3 years ago by s7r

Parent ID: #16645

#16645 is resolved, removing it as parent ticket so we can close it - it's not entirely related and this one is not urgent.

Last edited 3 years ago by s7r (previous) (diff)

comment:8 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:9 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:10 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:11 Changed 2 years ago by nickm

Resolution: wontfix
Status: assignedclosed
Note: See TracTickets for help on using tickets.