Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:37:36Zhttps://gitlab.torproject.org/legacy/trac/-/issues/10710new Project2020-06-13T16:37:36ZTracnew Projecttesting status support
[Penomet](http://penomet-hydropump.com/)
**Trac**:
**Username**: jahanamtesting status support
[Penomet](http://penomet-hydropump.com/)
**Trac**:
**Username**: jahanamDeliverable-May2011Peter EckersleyPeter Eckersleyhttps://gitlab.torproject.org/legacy/trac/-/issues/2760Proof of concept transport plugin: superencryption2020-06-13T18:33:53ZRoger DingledineProof of concept transport plugin: superencryptionNick started work on a socks proxy that will add its own layer of encryption on top of the Tor transport. The goal is to separate the task of making Tor unrecognizable on the wire from the task of achieving Tor's desired authentication a...Nick started work on a socks proxy that will add its own layer of encryption on top of the Tor transport. The goal is to separate the task of making Tor unrecognizable on the wire from the task of achieving Tor's desired authentication and confidentiality requirements.
I think asn picked it up from there, and it's now called obfsproxy.
One of its goals is to act as a proof of concept for our modular transport proposal (#2758), but I also want to actually ship it with the Tor bundles for users in blocking countries, so they have a chance against the next DPI-using adversary.
What's the current status? Is it ready to get its own Trac component and its own Tor git repository?Deliverable-May2011George KadianakisGeorge Kadianakishttps://gitlab.torproject.org/legacy/trac/-/issues/2759Proof of concept transport plugin: http headers2020-06-13T18:33:52ZRoger DingledineProof of concept transport plugin: http headersSteven has been working on a socks proxy that will stick the Tor transport in http headers. It isn't designed to fool a human looking at the traffic, but it seems to fool wireshark.
Its main goal is to act as a proof of concept for our ...Steven has been working on a socks proxy that will stick the Tor transport in http headers. It isn't designed to fool a human looking at the traffic, but it seems to fool wireshark.
Its main goal is to act as a proof of concept for our modular transport proposal (#2758) so we don't have to generalize from zero data points.Deliverable-May2011Steven MurdochSteven Murdochhttps://gitlab.torproject.org/legacy/trac/-/issues/2534get torperf output up on metrics website2020-06-13T17:49:41ZRoger Dingledineget torperf output up on metrics websiteKarsten, please revise this text to enumerate what torperf data there is that isn't getting recorded (or rather, that wasn't getting recorded as of Dec 1), and a plan for getting it archived on the metrics page.
For example,
https://met...Karsten, please revise this text to enumerate what torperf data there is that isn't getting recorded (or rather, that wasn't getting recorded as of Dec 1), and a plan for getting it archived on the metrics page.
For example,
https://metrics.torproject.org/data.html#performanceDeliverable-May2011Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/2533Export bwauth files for posterity2020-06-13T16:18:26ZRoger DingledineExport bwauth files for posterityThe bandwidth authorities track their progress with myriad internal files. What values here are worth saving for the metrics archive? Is there redundancy? Are there things we should write down that we're not writing down, or calculations...The bandwidth authorities track their progress with myriad internal files. What values here are worth saving for the metrics archive? Is there redundancy? Are there things we should write down that we're not writing down, or calculations we should do based on the raw data to produce more useful results?
Perhaps we should write some scripts that parse the internal files into posterity-worthy exportable files?Deliverable-May2011Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/1758Microdescriptors: make clients use microdescriptors instead of router descrip...2020-06-13T14:05:28ZNick MathewsonMicrodescriptors: make clients use microdescriptors instead of router descriptorsThe microdescriptor project ([#1748]) will be done once clients finally use microdescriptors, instead of regular ones, to choose routers and build circuits.
This step needs to come last in the microdescriptor project; it's mainly going ...The microdescriptor project ([#1748]) will be done once clients finally use microdescriptors, instead of regular ones, to choose routers and build circuits.
This step needs to come last in the microdescriptor project; it's mainly going to be figuring out every fool thing we do that requires a routerinfo_t , and making sure that node_t can do it as well using microdescriptor_t.Deliverable-May2011Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/1756Microdescriptors: clients can fetch and store microdesc consensuses and micro...2020-06-13T14:05:27ZNick MathewsonMicrodescriptors: clients can fetch and store microdesc consensuses and microdescsTo implement microdescriptors (see proposals 158 and 162), we'll need clients to fetch and store microdescriptors and microdescriptor consensuses. The code here will be almost completely the same as that used by caches; see tickets [#17...To implement microdescriptors (see proposals 158 and 162), we'll need clients to fetch and store microdescriptors and microdescriptor consensuses. The code here will be almost completely the same as that used by caches; see tickets [#1754] and [#1755].Deliverable-May2011Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/1748Implement microdescriptors2020-06-13T14:13:02ZNick MathewsonImplement microdescriptorsMicrodescriptors are a feature designed to greatly reduce the amount of data that needs to be transmitted to implement the Tor directory protocol. See [proposal 158 "Microdescriptors"](https://gitweb.torproject.org/tor.git/blob_plain/HE...Microdescriptors are a feature designed to greatly reduce the amount of data that needs to be transmitted to implement the Tor directory protocol. See [proposal 158 "Microdescriptors"](https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/doc/spec/proposals/158-microdescriptors.txt) and [proposal 162 "Publish the consensus in multiple flavors"](https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/doc/spec/proposals/162-consensus-flavors.txt) for design details.
There's an initial implementation at the server level (authorities generate microdescriptors and the appropriately flavored consensus).
We need to implement the remaining server and client components for May 1 2011.Deliverable-May2011Nick MathewsonNick Mathewson