Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:06:18Zhttps://gitlab.torproject.org/legacy/trac/-/issues/1901Add NAT-PMP support to tor-fw-helper.c2020-06-13T14:06:18ZJacob AppelbaumAdd NAT-PMP support to tor-fw-helper.cCurrently tor-fw-helper.c does not support NAT-PMP and it should.
We should add an autoconf flag to Tor's configure to enable linking against libnatpmp: '--enable-nat-pmp'Currently tor-fw-helper.c does not support NAT-PMP and it should.
We should add an autoconf flag to Tor's configure to enable linking against libnatpmp: '--enable-nat-pmp'Deliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1761Add support for bufferevent-based transports2020-06-13T14:05:29ZNick MathewsonAdd support for bufferevent-based transportsWe've been planning for a while to move Tor's transport mechanism from using our own buf_t implementation to Libevent's bufferevents, which in Libevent 2.0 allow us to use IOCP on windows, full scatter/gather IO, and other useful things....We've been planning for a while to move Tor's transport mechanism from using our own buf_t implementation to Libevent's bufferevents, which in Libevent 2.0 allow us to use IOCP on windows, full scatter/gather IO, and other useful things.
The latest version of the code is in the highest-numbered "bufferevent*" branch in my public repository, currently bufferevent3.Deliverable-Sep2010Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/1902Add UPnP support to tor-fw-helper.c2020-06-13T14:06:18ZJacob AppelbaumAdd UPnP support to tor-fw-helper.cCurrently tor-fw-helper.c does not support UPnP and it should.
We should add an autoconf flag to Tor's configure to enable linking against libminiupnpc: '--enable-upnp'Currently tor-fw-helper.c does not support UPnP and it should.
We should add an autoconf flag to Tor's configure to enable linking against libminiupnpc: '--enable-upnp'Deliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1721Analyze increase in Microsoft Windows relay availability?2020-06-13T17:49:31ZAndrew LewmanAnalyze increase in Microsoft Windows relay availability?In the past two years, have relays claiming to be microsoft windows had increased uptime? I'm trying to determine if bug #98 is effectively resolved, because the empirical evidence shows that the average uptime of relays has increased o...In the past two years, have relays claiming to be microsoft windows had increased uptime? I'm trying to determine if bug #98 is effectively resolved, because the empirical evidence shows that the average uptime of relays has increased over the past 2 years.Deliverable-Sep2010Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/1918annotate torperf output with paths2020-06-13T17:49:35ZRoger Dingledineannotate torperf output with pathsTorperf's results right now represent the average performance that users should expect to see. But part of the problem with the Tor network right now is that the variance is high. One component contributing to this variance is the fact t...Torperf's results right now represent the average performance that users should expect to see. But part of the problem with the Tor network right now is that the variance is high. One component contributing to this variance is the fact that different users choose different entry guards. It seems clear that Tor network performance is a function of (among other things) the entry guards you've picked.
There's lots of analysis we should do to try to learn more about what performance you should expect from having which guards. A prerequisite for all of this analysis is knowing which first hop is used in each torperf run.
So we should modify torperf to annotate in its logs what path was chosen for that request. (For now, we only really want the first hop; but I bet we'll find a good use for knowing the other hops too.)Deliverable-Sep2010Sebastian HahnSebastian Hahnhttps://gitlab.torproject.org/legacy/trac/-/issues/1925Create and Record All Tor Chrome Issues on Chromium Bugtracker2020-06-13T00:14:25ZMike PerryCreate and Record All Tor Chrome Issues on Chromium BugtrackerWe should convert my Chrome Extensions mailinglist posts into tickets in their bugtracker, and list those and all other relevant Chrome tickets here. A number have been getting mixed in into ticket #1816. They should be listed here instead.We should convert my Chrome Extensions mailinglist posts into tickets in their bugtracker, and list those and all other relevant Chrome tickets here. A number have been getting mixed in into ticket #1816. They should be listed here instead.Deliverable-Sep2010Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/1900Create tor-fw-helper.c2020-06-13T14:06:17ZJacob AppelbaumCreate tor-fw-helper.ctor-fw-helper.c should support upnp and nat-pmp; it should be written in such a way that output from tor-fw-helper.c will be machine parsed without too much trouble.tor-fw-helper.c should support upnp and nat-pmp; it should be written in such a way that output from tor-fw-helper.c will be machine parsed without too much trouble.Deliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1757Microdescriptors: abstract the notion of "Tor node" in the code2020-06-13T14:05:27ZNick MathewsonMicrodescriptors: abstract the notion of "Tor node" in the codeRight now we have at least 5 things that we use to indicate a Tor node:
* A `const char *` pointing to an ID key digest
* A `routerinfo_t`
* A `routerstatus_t`
* An `extend_info_t`
* An entry in `rephist.c`, though those are mostly...Right now we have at least 5 things that we use to indicate a Tor node:
* A `const char *` pointing to an ID key digest
* A `routerinfo_t`
* A `routerstatus_t`
* An `extend_info_t`
* An entry in `rephist.c`, though those are mostly isolated.
For microdescriptors, we're about to add another thing:
* A `microdescriptor_t`
Making our code work properly with all of these variant things is already a bit hairy. It sure would be nice if we had some kind of abstract node_t that could make it so our code worked well with all of the above.
First, we'll need a basic design here. At the minimum we should make routerstatus_t and routerinfo_t (basically) immutable, and add a node_t that abstracts routerstatus_t and routerinfo_t. Then, we can make it so that its interface can be satisfied by microdescriptor_t as well.Deliverable-Sep2010Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/1755Microdescriptors: caches fetch and serve microdescriptors2020-06-13T14:05:26ZNick MathewsonMicrodescriptors: caches fetch and serve microdescriptorsFor microdescriptors to work, clients need to be able to fetch them from the caches. Thus, caches need to fetch microdescriptors and serve them. This is mostly implemented in my "microdesc_dl" branch, but depends on [#1754].
The "cach...For microdescriptors to work, clients need to be able to fetch them from the caches. Thus, caches need to fetch microdescriptors and serve them. This is mostly implemented in my "microdesc_dl" branch, but depends on [#1754].
The "caches fetch and store microdescriptors" code will be reusable for clients.Deliverable-Sep2010Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/1754Microdescriptors: caches fetch and server all flavors of consensus2020-06-13T14:05:25ZNick MathewsonMicrodescriptors: caches fetch and server all flavors of consensusRight now, caches only know how to download and use one single consensus flavor. We need them to be able to fetch, parse, store, and serve every flavor. Right now, that means "normal" and "microdesc".
Storing and serving are already i...Right now, caches only know how to download and use one single consensus flavor. We need them to be able to fetch, parse, store, and serve every flavor. Right now, that means "normal" and "microdesc".
Storing and serving are already implemented (I believe) since authorities do them. Parsing and fetching remain are partially implemented in my "microdesc_dl" branch.
See proposals 158 and 162 for more information.Deliverable-Sep2010Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/1759Microdescriptors: clean out the microdescriptor cache when it gets too big2020-06-13T14:05:28ZNick MathewsonMicrodescriptors: clean out the microdescriptor cache when it gets too bigThe current microdescriptor fetching/cacheing code has no idea of how to forget about microdescriptors once they're too old. Doing this for router descriptors has been a major pain since, like, forever. We should design this more caref...The current microdescriptor fetching/cacheing code has no idea of how to forget about microdescriptors once they're too old. Doing this for router descriptors has been a major pain since, like, forever. We should design this more carefully so that we don't replace one maintenance headache with two.Deliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1830perconnbwrate/burst not reset when config options change2020-06-13T14:05:56ZRoger Dingledineperconnbwrate/burst not reset when config options changeIf I have perconnbwrate/burst set to something, and an OR conn arrives, the rate and burst for that conn are chosen forevermore at that moment. If I later change the config options and hup, new OR conns get the new options, but old ones ...If I have perconnbwrate/burst set to something, and an OR conn arrives, the rate and burst for that conn are chosen forevermore at that moment. If I later change the config options and hup, new OR conns get the new options, but old ones stay as they are.
This is going to become even more apparent once we put the options in the consensus. Our experiments won't produce the results we want because they'll be spoiled by already-established OR conns.
So we should walk through all the OR conns whenever those options change (including if they change in the consensus), and reset rate and burst to the new rate and burst, and if the bucket is now higher than burst, set it back to burst too.Deliverable-Sep2010Roger DingledineRoger Dingledinehttps://gitlab.torproject.org/legacy/trac/-/issues/9712Persian Tor short manual should be right-to-left2020-06-13T17:21:15ZVeggie MonsterPersian Tor short manual should be right-to-leftSomebody with website access should go to
https://www.torproject.org/dist/manual/short-user-manual_fa.xhtml
And adds dir="rtl" to the <html> tag first line like this:
<html dir="rtl">
It is critical cause in current situation latin c...Somebody with website access should go to
https://www.torproject.org/dist/manual/short-user-manual_fa.xhtml
And adds dir="rtl" to the <html> tag first line like this:
<html dir="rtl">
It is critical cause in current situation latin characters break the word ordering and make it unreadable (it is not just that it is left aligned).Deliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1766Project: "Improve TorPerf for more accurate measurements."2020-06-13T17:49:32ZNick MathewsonProject: "Improve TorPerf for more accurate measurements."We have a 30 September deliverable to make TorPerf more accurate. Andrew says _there was some todo list to make torperf behave like a real tor client. iirc something about it ignoring guards and cbt._
Step one here is to get more clari...We have a 30 September deliverable to make TorPerf more accurate. Andrew says _there was some todo list to make torperf behave like a real tor client. iirc something about it ignoring guards and cbt._
Step one here is to get more clarity about what the deliverable means, and what part of it is deliverable in September, then to edit this description as appropriate.
Child Tickets:
[[TicketQuery(parent=#1766)]]Deliverable-Sep2010Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/1762Project: Automated translation seeding2020-06-13T17:32:28ZNick MathewsonProject: Automated translation seedingFor our 30 September deliverable date, we need to make some progress on "automated translation seeding."
Runa asked "Are you talking about Google translator toolkit and Worldwide Lexicon?" And perhaps that is what Phobos was talking ab...For our 30 September deliverable date, we need to make some progress on "automated translation seeding."
Runa asked "Are you talking about Google translator toolkit and Worldwide Lexicon?" And perhaps that is what Phobos was talking about, but perhaps not.
The first step here is to describe what the long-term requirement is, and what the September 30 requirement is, and edit this description to contain them.
Child tickets:
[[TicketQuery(parent=#1762)]]Deliverable-Sep2010Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/1768Project: Evaluate and deploy improved TorWeather2020-06-13T18:11:12ZNick MathewsonProject: Evaluate and deploy improved TorWeatherOur friends at Wesleyan have finished an overhaul of the TorWeather system. We need to evaluate it and deploy it as appropriate for our 30Sep deliverables.
Child Tickets:
[[TicketQuery(parent=#1768)]]Our friends at Wesleyan have finished an overhaul of the TorWeather system. We need to evaluate it and deploy it as appropriate for our 30Sep deliverables.
Child Tickets:
[[TicketQuery(parent=#1768)]]Deliverable-Sep2010Christian FrommeChristian Frommehttps://gitlab.torproject.org/legacy/trac/-/issues/1767Project: Integrate exit scanner improvements2020-06-13T16:18:17ZNick MathewsonProject: Integrate exit scanner improvementsWe have a september 30 deliverable currently listed as: "Exit scanner - in process, still undergoing more work, has a Google Summer of Code student working on it now"
Step one here is to get more clarity about the final deliverables, an...We have a september 30 deliverable currently listed as: "Exit scanner - in process, still undergoing more work, has a Google Summer of Code student working on it now"
Step one here is to get more clarity about the final deliverables, and the Sep 30 deliverables. Are they just a matter of integrating the GSoC improvements, or is more needed?
Child Tickets:
[[TicketQuery(parent=#1767)]]Deliverable-Sep2010Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/1764Project: Launch the improved website2020-06-13T17:18:29ZNick MathewsonProject: Launch the improved websiteAt the end of our [milestone:"Tor Website Overhaul" website overhaul efforts], we should finally launch the new website on torproject.org.
Tickets labeled for "Tor Website Overhaul":
[[TicketQuery(milestone=Tor Website Overhaul)]]
Chil...At the end of our [milestone:"Tor Website Overhaul" website overhaul efforts], we should finally launch the new website on torproject.org.
Tickets labeled for "Tor Website Overhaul":
[[TicketQuery(milestone=Tor Website Overhaul)]]
Child tickets:
[[TicketQuery(parent=#1764)]]Deliverable-Sep2010Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/legacy/trac/-/issues/1751Project: Make it harder to use exits as one-hop proxies2020-06-13T14:05:24ZNick MathewsonProject: Make it harder to use exits as one-hop proxies[Proposal 163](https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/doc/spec/proposals/163-detecting-clients.txt) outlined some ways to detect clients, and [later emails](http://archives.seul.org/or/dev/Jun-2009/msg00018.html) elaborat...[Proposal 163](https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/doc/spec/proposals/163-detecting-clients.txt) outlined some ways to detect clients, and [later emails](http://archives.seul.org/or/dev/Jun-2009/msg00018.html) elaborated on the issue, clarifying some parts and exposing hopeless muddiness in others.
There's an initial implementation of a variant of the concept in Tor now, under the RefuseUnknownExits configuration option. Unfortunately, turning it on seems to give many positives. We haven't investigated whether they're false positives or just jerks using Tor as a one-hop proxy.
Child Tickets:
[[TicketQuery(parent=#1751)]]Deliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1763Project: publish "10 things to think about circumvention systems" whitepaper2010-09-28T17:50:19ZNick MathewsonProject: publish "10 things to think about circumvention systems" whitepaperRoger wrote a draft whitepaper here. We should get it into publishable format so that it can get more attention.Roger wrote a draft whitepaper here. We should get it into publishable format so that it can get more attention.Deliverable-Sep2010Andrew LewmanAndrew Lewman