Write a proposal for using a front-end proxy like apache for bridge scanning resistance
Item 18 from org/sponsors/SponsorF/Year2 is: "write a proposal for at what level of abstraction the "Tor does an SSL handshake with a real apache, posts a password over http to the server, and then gets passed to the real Tor relay" design should take place. Should the Tor client simply talk to a local proxy which does this dance, a la pluggable transports? Should Tor use a libevent2 filter? Something else?"
Nick and I talked about this deliverable last December. Nick thought that writing a proposal is doable. He didn't have a specific design in mind, but he didn't see any obstacles to writing one. He said we should definitely be working on this stuff earlier, not later. I said I'd assign the project ticket to Nick and to the July milestone, which I'm doing now.
I'm also cc'ing asn and ioerror who both expressed interest in working on this deliverable.