Opened 5 years ago

Last modified 2 years ago

#15232 new defect

Specify a potential TLS-replacing protocol for future use in Tor.

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: SponsorZ, needs-proposal, spec sponsor3-maybe
Cc: yawning Actual Points:
Parent ID: Points: large
Reviewer: Sponsor:

Description

We should wrap up the design stuff on v0 of "tentp", and rename it.

Child Tickets

Change History (14)

comment:1 Changed 5 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.2.7.x-final

Worth looking at during 0.2.7 triage IMO

comment:2 Changed 5 years ago by nickm

Status: newassigned

comment:3 Changed 4 years ago by nickm

Keywords: 027-triaged-1-in added

Marking more tickets as triaged-in for 0.2.7

comment:4 Changed 4 years ago by isabela

Points: large
Version: Tor: 0.2.7

comment:5 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:6 Changed 4 years ago by nickm

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

These

comment:7 Changed 3 years ago by teor

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

Milestone renamed

comment:8 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:9 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:10 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:11 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:12 Changed 2 years ago by nickm

Keywords: 027-triaged-1-in removed

comment:13 Changed 2 years ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:14 Changed 2 years ago by nickm

Keywords: sponsor3-maybe added
Severity: Normal
Note: See TracTickets for help on using tickets.