Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:21:15Zhttps://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/6985Tor, .torrents, Freedom2020-06-13T17:20:36ZTracTor, .torrents, FreedomHi.
I was seeding Tor project, bundle, obfs and Tails on my Seedbox (along with many many other Anti-Censorship applications) for couple of mounts. Unfortunately you don't provide public _.torrent_ files any more -except for Tails- and i...Hi.
I was seeding Tor project, bundle, obfs and Tails on my Seedbox (along with many many other Anti-Censorship applications) for couple of mounts. Unfortunately you don't provide public _.torrent_ files any more -except for Tails- and it's useless if I seed personal-made torrent files when no one else has them.
Please add torrent files to download section again.
**Trac**:
**Username**: CipherDeliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1974TorCtl.ConsensusTracker should track NS events too2010-09-30T23:11:14ZMike PerryTorCtl.ConsensusTracker should track NS events tooWe need to have two modes for TorCtl.ConsensusTracker, one mode that just tracks the actual consensus router set, and another mode that tracks the set of routers the Tor client actually believes are running. There may also be a bug in th...We need to have two modes for TorCtl.ConsensusTracker, one mode that just tracks the actual consensus router set, and another mode that tracks the set of routers the Tor client actually believes are running. There may also be a bug in the Tor client that causes it not to generate NEWDESC events for routers it thinks are not Running..
TorBEL and the scanners need to use this first mode, but the script for 1919 needs to use the second mode.Deliverable-Sep2010https://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/1919Set up a few new torperfs with fixed sets of entry guards2020-06-13T17:49:36ZRoger DingledineSet up a few new torperfs with fixed sets of entry guardsIn theory, the results of #1918 (annotate torperf fetches by path) should let us simulate the expected performance of Tor users that use various combinations of guard nodes: just grab all the requests that use the guards you're simulatin...In theory, the results of #1918 (annotate torperf fetches by path) should let us simulate the expected performance of Tor users that use various combinations of guard nodes: just grab all the requests that use the guards you're simulating using, and make a torperf graph out of just those requests.
The problem is that the CBT feature will alter Tor's circuit build timeout based on the average build times of all nodes, not just the guards we're pretending we used, so we won't be able to capture the whole picture.
How different will the results be? To get some intuition, we should run several torperf install with cbt enabled and various sets of guards. Then when we have enough annotated torperf runs, we'll be able to compare the simulated results with the actual results, and make some decisions about what went wrong.
So the first question is: what combinations of guards should we try using? Mike, do you have any good guesses here?Deliverable-Sep2010Sebastian HahnSebastian Hahnhttps://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/1905Test UPnP support in tor-fw-helper.c2020-06-13T14:06:20ZJacob AppelbaumTest UPnP support in tor-fw-helper.cWe should ensure that UPnP support is tested with at least one popular router and probably also with the UPnP IGD software that runs on Gnu/Linux.We should ensure that UPnP support is tested with at least one popular router and probably also with the UPnP IGD software that runs on Gnu/Linux.Deliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1904Test NAT-PMP support in tor-fw-helper.c2020-06-13T14:06:20ZJacob AppelbaumTest NAT-PMP support in tor-fw-helper.cWe should ensure that NAT-PMP support is tested with at least one popular router and probably also with the NAT-PMP IGD software that runs on Gnu/Linux.We should ensure that NAT-PMP support is tested with at least one popular router and probably also with the NAT-PMP IGD software that runs on Gnu/Linux.Deliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1903Teach Tor to control networks with tor-fw-helper.c2020-06-13T14:37:11ZJacob AppelbaumTeach Tor to control networks with tor-fw-helper.cCurrently, Tor does not have the ability to control upstream firewalls to enable port forwarding for various server modes.
Tor should use tor-fw-helper.c to assist with network port forwarding when it finds itself unreachable by the gen...Currently, Tor does not have the ability to control upstream firewalls to enable port forwarding for various server modes.
Tor should use tor-fw-helper.c to assist with network port forwarding when it finds itself unreachable by the general internet.Deliverable-Sep2010https://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/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/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/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/1782SponsorD languages to add to Translation portal2020-06-13T17:32:29ZTracSponsorD languages to add to Translation portalSpanish: Vidalia Help
Arabic: Vidalia Help
Burmese: Orbot, Vidalia Help
Persian: Torcheck, Vidalia Help
**Trac**:
**Username**: carolynSpanish: Vidalia Help
Arabic: Vidalia Help
Burmese: Orbot, Vidalia Help
Persian: Torcheck, Vidalia Help
**Trac**:
**Username**: carolynDeliverable-Sep2010https://gitlab.torproject.org/legacy/trac/-/issues/1771Project: Write up integration requirements for Tor, Torbutton, and Firefox Pr...2010-09-21T02:31:02ZNick MathewsonProject: Write up integration requirements for Tor, Torbutton, and Firefox Private ModeWe've got a long-term goal of getting Tor and Torbutton "integrated" (whatever that means!) with Firefox's private browsing mode. Phobos says: "We talked to Mozilla about this, they are excited, but needs lots of coding on their end, c...We've got a long-term goal of getting Tor and Torbutton "integrated" (whatever that means!) with Firefox's private browsing mode. Phobos says: "We talked to Mozilla about this, they are excited, but needs lots of coding on their end, can't be done by September." Nevertheless, we should at least summarize the issues and requirements here so that we know what we need to do and what Mozilla needs to do for this to be feasible.
This is a 30 Sep deliverable.Deliverable-Sep2010Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/1770Project: Write up a want-list for missing features in Chrome2020-06-12T23:51:14ZNick MathewsonProject: Write up a want-list for missing features in ChromeBefore we can support Chrome, we need them to make some changes in their browser. Step one here is to write up the list of enhancements we need so that the chrome team (and others) can start working on them.
This is a 30 September deli...Before we can support Chrome, we need them to make some changes in their browser. Step one here is to write up the list of enhancements we need so that the chrome team (and others) can start working on them.
This is a 30 September deliverable.
Child tickets:
[[TicketQuery(parent=#1770)]]Deliverable-Sep2010Mike PerryMike Perryhttps://gitlab.torproject.org/legacy/trac/-/issues/1769Project: Release a new alpha Torbutton with koryk's work integrated2010-09-30T22:58:44ZNick MathewsonProject: Release a new alpha Torbutton with koryk's work integratedWe have a 30 September deliverable to release a new alpha of Torbutton, ideally including (most? all?) of koryk's work, plus other enhancements as appropriate.
Child tickets:
[[TicketQuery(parent=#1769)]]We have a 30 September deliverable to release a new alpha of Torbutton, ideally including (most? all?) of koryk's work, plus other enhancements as appropriate.
Child tickets:
[[TicketQuery(parent=#1769)]]Deliverable-Sep2010Mike PerryMike Perryhttps://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/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 Loesing