Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#4958 closed project (implemented)

Make a plan for a possibly revised proposal 179 integration

Reported by: karsten Owned by: nickm
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords: SponsorF20120315 tor-client
Cc: nickm, ioerror, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


In sponsor F deliverable 5 we promised to "make and maybe blog about a plan for proposal 179 integration and the censorship arms race. Proposal 179 is the 'here are hundreds of ways to change our SSL certs to not stand out as much compared to normal SSL certs' proposal. How much should we fix preemptively, and when?"

Roger is increasingly of the opinion that we should leave the low-hanging fruit in place to avoid being blocked in a worse way. It's also unclear whether blogging about our plans and being too public about it is a good idea. However, having a better understanding of the types of blocking vulnerabilities and how to respond to possible blockings would be good.

As of December 2011, the implementation status of proposal 179 is that one part got merged, another part got built, the part that Nick thinks will help most isn't built, some parts are a bad idea, and some good ideas are not in the proposal. Maybe we need to come up with a revised proposal 179.

Here are a few possible next steps:

  • Discuss a possible revised proposal 179 on tor-dev.
  • Make a plan which parts of the proposal we want to integrate now vs. later.

Child Tickets

Change History (6)

comment:1 Changed 8 years ago by karsten

Owner: set to nickm
Status: newassigned

Nick says that as long as the deliverable is about making a plan for an improved proposal 179 thing, but not necessarily integrating it, he'll kick off the discussion on tor-dev. Assigning the ticket to him.

comment:2 Changed 8 years ago by nickm

I've written a draft in my torspec repo in a branch called "again_normalize_certs". I'm bouncing it off the 179 authors; if they don't object to my leaving their names on it, I'll send it to tor-dev with minor typo fixes.

comment:3 Changed 8 years ago by nickm

Resolution: implemented
Status: assignedclosed

It's approved by the 179 authors; committed it to torspec and sent it to tor-dev.

comment:4 Changed 8 years ago by karsten

Keywords: SponsorF20120315 added
Milestone: Sponsor F: March 15, 2012

Switching from using milestones to keywords for sponsor deliverables. See #6365 for details.

comment:5 Changed 8 years ago by nickm

Keywords: tor-client added

comment:6 Changed 8 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.