Make a plan for a possibly revised proposal 179 integration
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.