The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2021-09-16T14:21:52Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/40136Revise doc/state-contents.txt to be accurate2021-09-16T14:21:52ZNick MathewsonRevise doc/state-contents.txt to be accurateThe doc/state-contents.txt file is out of date, and missing a bunch of documentation.
We should have accurate documentation for all of the state file's contents.
The following elements are undocumented:
* BWHistoryIPv6ReadEnds
* BWHi...The doc/state-contents.txt file is out of date, and missing a bunch of documentation.
We should have accurate documentation for all of the state file's contents.
The following elements are undocumented:
* BWHistoryIPv6ReadEnds
* BWHistoryIPv6ReadInterval
* BWHistoryIPv6ReadValues
* BWHistoryIPv6ReadMaxima
* BWHistoryIPv6WriteEnds
* BWHistoryIPv6WriteInterval
* BWHistoryIPv6WriteValues
* BWHistoryIPv6WriteMaxima
* Guard
* TotalBuildTimes
* CircuitBuildAbandonedCount
* "CircuitBuildTimeBin"
* "BuildtimeHistogram"
* "MinutesSinceUserActivity"
* "Dormant"
The follow elements are obsolete:
* "EntryGuard"
* "EntryGuardDownSince"
* "EntryGuardUnlistedSince"
* "EntryGuardAddedBy"
These are obsolete _and_ undocumented:
* "EntryGuardPathBias"
* "EntryGuardPathUseBias"
* HidServRevCounterTor: 0.4.5.x-freezeNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/web/manual/-/issues/43F-Droid should be written with a capital D2020-10-13T19:14:36ZGusF-Droid should be written with a capital DA translator reported that:
"F-Droid should be written with a capital D."
http://dgvdmophvhunawds.onion/mobile-tor/index.htmlA translator reported that:
"F-Droid should be written with a capital D."
http://dgvdmophvhunawds.onion/mobile-tor/index.htmlhttps://gitlab.torproject.org/tpo/web/support/-/issues/120Incorrect GPGTools link2020-09-18T15:53:54ZGusIncorrect GPGTools linkFrom frontdesk:
Hello! This weblink (https://www.gpgtools.org) leads to a security risk site. I believe it needs to link to this site instead: https://gpgtools.org/From frontdesk:
Hello! This weblink (https://www.gpgtools.org) leads to a security risk site. I believe it needs to link to this site instead: https://gpgtools.org/GusGushttps://gitlab.torproject.org/tpo/web/manual/-/issues/42In Mobile Tor section, we should link tickets to GitLab2020-12-01T10:04:16ZGusIn Mobile Tor section, we should link tickets to GitLabUpdate Trac links to GitLab links, so users can follow the issue status.
https://tb-manual.torproject.org/mobile-tor/Update Trac links to GitLab links, so users can follow the issue status.
https://tb-manual.torproject.org/mobile-tor/https://gitlab.torproject.org/tpo/tpa/team/-/issues/40045Make (and update) a services table, with pointers to survival guides for each...2020-09-23T15:15:25ZRoger DingledineMake (and update) a services table, with pointers to survival guides for each serviceWe should make a table of what our services are, and which teams / people are running them.
Here's the original table:
https://trac.torproject.org/projects/tor/wiki/org/operations/services
ahf imported this table into gitlab, but it d...We should make a table of what our services are, and which teams / people are running them.
Here's the original table:
https://trac.torproject.org/projects/tor/wiki/org/operations/services
ahf imported this table into gitlab, but it doesn't seem to display:
https://gitlab.torproject.org/legacy/trac/-/wikis/org/operations/Infrastructure
I'll start with: phw just made a survival guide for check, and it is at:
https://gitlab.torproject.org/tpo/metrics/team/-/wikis/Survival-Guides/Checkanarcatanarcathttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/40015Bandwidth file spec v1.5 adds Tor version but sbws adds Tor version with band...2020-12-07T11:12:02ZjugaBandwidth file spec v1.5 adds Tor version but sbws adds Tor version with bandwidth file spec as v1.4Reported by @atagar in irc #tor-dev:
```
22:53 <+ atagar> juga, karsten: Our bandwidth file spec says that the most recent version is 1.5.0 to add a tor_version attribute (https://gitweb.torproject.org/torspec.git/commit/?id=7d8b4bc)...Reported by @atagar in irc #tor-dev:
```
22:53 <+ atagar> juga, karsten: Our bandwidth file spec says that the most recent version is 1.5.0 to add a tor_version attribute (https://gitweb.torproject.org/torspec.git/commit/?id=7d8b4bc). However,
CollecTor's most recent bandwidth files (https://collector.torproject.org/recent/relay-descriptors/bandwidths/) say that they're version 1.4.0 yet include a tor_version. Maybe our bandwidth
scanners added this
22:53 <+ atagar> attribute without updating their version number?
22:54 <+ atagar> If so since this has been live for a while we should probably simply change the spec to say that tor_version is a 1.4.0 attribute, and that we don't have a version 1.5.0.
```
probably we forgot to update the bandwidth file spec in the sbws's generated bandwidth file.
I'm not sure whether we should change it in the bandwidth spec or in sbws, since bandwidth spec also says v1.5 adds other things.sbws: 1.1.x-finalhttps://gitlab.torproject.org/tpo/web/tpo/-/issues/96Redirect 2019.www.torproject.org/docs/debian to support.tpo/apt2022-02-02T19:16:46ZGusRedirect 2019.www.torproject.org/docs/debian to support.tpo/aptLast year I migrated this documentation: https://2019.www.torproject.org/docs/debian to support.torproject.org/apt
We should create a new htaccess redirect for that URL to support portal.Last year I migrated this documentation: https://2019.www.torproject.org/docs/debian to support.torproject.org/apt
We should create a new htaccess redirect for that URL to support portal.https://gitlab.torproject.org/tpo/core/tor/-/issues/40101Revise all remaining trac.tpo URLs in Tor repository2021-07-22T16:18:20ZNick MathewsonRevise all remaining trac.tpo URLs in Tor repositoryNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/web/manual/-/issues/41In https visualization add onion services2024-03-21T18:53:39ZGusIn https visualization add onion servicesFeedback that we got from Frontdesk:
Machine translation:
"I was reading this: http://4bflp2c4tnynnbes.onion/es/https/https-1/
(specifically the diagram)
The diagram is quite good, it explains it excellently, however it would be quite n...Feedback that we got from Frontdesk:
Machine translation:
"I was reading this: http://4bflp2c4tnynnbes.onion/es/https/https-1/
(specifically the diagram)
The diagram is quite good, it explains it excellently, however it would be quite nice to add a switch for the hidden services (.onion).
What things can the hidden services see, because they don't need HTTPS because they are encrypted by default."
"Estaba leyendo esto: http://4bflp2c4tnynnbes.onion/es/https/https-1/
(especificamente el diagrama)
El diagrama está bastante bien, lo explica de forma excelente, sin
embargo estaría bastante bien que se añadiese un interruptor para los
servicios ocultos (.onion). Que cosas pueden ver los servicios
ocultos, debido a que estos no necesitan HTTPS debido a que están
encriptados por defecto."https://gitlab.torproject.org/tpo/web/community/-/issues/151[Onion Services] Add new ways to deploy your onion site2021-03-25T15:07:32ZGus[Onion Services] Add new ways to deploy your onion site@Hiro developed different ways to deploy onion sites with terraform, heroku. We should promote it in a special page or/and update our docs to include it.
- [ ] terraform
- [x] ansible
- [ ] heroku@Hiro developed different ways to deploy onion sites with terraform, heroku. We should promote it in a special page or/and update our docs to include it.
- [ ] terraform
- [x] ansible
- [ ] herokuSponsor 84: Onion GuidesGusGushttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/40013Update documentation on what/where to check regarding bandwidth values/files2021-02-12T10:56:54ZjugaUpdate documentation on what/where to check regarding bandwidth values/filessbws: 1.1.x-finaljugajugahttps://gitlab.torproject.org/tpo/community/training/-/issues/6Add 'how to setup a private bridge' training slides2023-06-30T17:21:17ZGusAdd 'how to setup a private bridge' training slidesAdd to community.tpo/training/resources our private bridges slides.Add to community.tpo/training/resources our private bridges slides.GusGushttps://gitlab.torproject.org/tpo/core/tor/-/issues/40088DeepCorr: Strong Flow Correlation Attacks on Tor Using Deep Learning2022-02-28T19:41:51ZForboDeepCorr: Strong Flow Correlation Attacks on Tor Using Deep LearningI found this paper and have been trying to find any kind of official response. The claims of 96% correlation accuracy in as little as 900KB is extremely disconcerting.
https://arxiv.org/pdf/1808.07285v1.pdf
An email to the tor-dev maili...I found this paper and have been trying to find any kind of official response. The claims of 96% correlation accuracy in as little as 900KB is extremely disconcerting.
https://arxiv.org/pdf/1808.07285v1.pdf
An email to the tor-dev mailing list seemed to have generated no discussion, so I'm hoping that this issue will be more successful.
https://www.mail-archive.com/tor-dev@lists.torproject.org/msg10854.html
Their GitHub repo is here: https://github.com/SPIN-UMass/DeepCorrMike PerryMike Perryhttps://gitlab.torproject.org/tpo/web/support/-/issues/119Update "How to Report a Bug or Give Feedback" to reflect GitLab migration2020-08-27T16:33:24ZGusUpdate "How to Report a Bug or Give Feedback" to reflect GitLab migrationWe need to update this entry:
> Trac
>
> You can file a ticket at https://trac.torproject.org. We track all Tor Browser 9 related issues with the tbb-9.0-issues keyword. Tickets related to our website should be added with the component...We need to update this entry:
> Trac
>
> You can file a ticket at https://trac.torproject.org. We track all Tor Browser 9 related issues with the tbb-9.0-issues keyword. Tickets related to our website should be added with the component "Webpages/Website."
https://support.torproject.org/misc/bug-or-feedback/c1e0c1e0https://gitlab.torproject.org/tpo/web/support/-/issues/118support.torproject page regarding IRC points to the trac.torproject page2022-03-01T18:41:59Zroyaljellysupport.torproject page regarding IRC points to the trac.torproject pageThe 'IRC Block Tracker' page referenced in [this support page](https://support.torproject.org/abuse/tor-ban-irc/) points to the [Blocking IRC page on trac](https://trac.torproject.org/projects/tor/wiki/doc/BlockingIrc), which is outdated...The 'IRC Block Tracker' page referenced in [this support page](https://support.torproject.org/abuse/tor-ban-irc/) points to the [Blocking IRC page on trac](https://trac.torproject.org/projects/tor/wiki/doc/BlockingIrc), which is outdated.
- [ ] Move wiki page in legacy to the main gitlab wiki http://eweiibe6tdjsdprb4px6rqrzzcsi22m4koia44kc5pcjr7nec2rlxyad.onion/legacy/trac/-/wikis/doc/BlockingIrc . It can be move to this wiki for now: http://eweiibe6tdjsdprb4px6rqrzzcsi22m4koia44kc5pcjr7nec2rlxyad.onion/tpo/team
- [ ] Change documentationhttps://gitlab.torproject.org/tpo/core/torspec/-/issues/27Tor control spec doesn't properly specify reply format2022-02-21T19:12:26ZcypherpunksTor control spec doesn't properly specify reply formatThe control spec does not sufficiently specify how to generically parse multi line replies from the controller. The intent seems to be that multi line response data is terminated by a '.' line.
However, this is not specified in the con...The control spec does not sufficiently specify how to generically parse multi line replies from the controller. The intent seems to be that multi line response data is terminated by a '.' line.
However, this is not specified in the control spec section 2.3 and the reply description there is insufficient to properly recognize multi-line reply packets leading to bugs like:
https://trac.torproject.org/projects/tor/ticket/16990https://gitlab.torproject.org/tpo/core/torspec/-/issues/26torspec references UTC, but tor uses unix time (leap second handling)2022-02-21T19:13:04Zteortorspec references UTC, but tor uses unix time (leap second handling)When the various torspec documents specify time, they refer to UTC. But the implementations used by at least Linux, *BSD and OS X are based on the Unix time epoch.
This makes a difference to how leap seconds are handled: UTC includes le...When the various torspec documents specify time, they refer to UTC. But the implementations used by at least Linux, *BSD and OS X are based on the Unix time epoch.
This makes a difference to how leap seconds are handled: UTC includes leap seconds, but unix time excludes them.
We should:
* ensure that none of the security properties of tor depend on leap seconds either being present or absent, either individually or in aggregate:
* every minute is not 60 seconds long (and equivalently for hour, day, week)
* some epoch times can repeat or be missing
* UTC and Unix time differ by approximately 30 seconds
* check how the current Linux, BSD, Windows and OS X implementations handle leap seconds (in roughly that order of priority)
* consider and document tor's handling of leap seconds
See:
* https://en.wikipedia.org/wiki/Leap_second
* https://en.wikipedia.org/wiki/Unix_timehttps://gitlab.torproject.org/tpo/core/torspec/-/issues/24PT_LOG and PT_STATUS event fields unspecifed2022-02-21T19:12:25ZDamian JohnsonPT_LOG and PT_STATUS event fields unspecifedRecently Tor added PT_LOG and PT_STATUS events to the spec...
https://gitweb.torproject.org/torspec.git/commit/?id=3028cf1
https://gitweb.torproject.org/torspec.git/commit/?id=b38257e
Unfortunately the 'pt-spec.txt section 3.3.5' secti...Recently Tor added PT_LOG and PT_STATUS events to the spec...
https://gitweb.torproject.org/torspec.git/commit/?id=3028cf1
https://gitweb.torproject.org/torspec.git/commit/?id=b38257e
Unfortunately the 'pt-spec.txt section 3.3.5' section they mention does not exist, and in looking around I can't find anything that describes what these event fields are defined as ('PT=' 'TYPE=', 'CONNECT=', etc).
I started to write a stem parser for these but can't continue until this is done (I can't parse events without knowing what fields they include).
David is aware of this and plans to has kindly offered to add the missing info...
```
22:24 <+atagar> dgoulet: Your control-spec addition to descript PT_LOG and PT_STATUS
cite a pt-spec section 3.3.4 which does not exist.
22:24 <+atagar> s/descript/describe
22:29 <+atagar> dgoulet: Huh. I'm not spotting anything that lists the keyword
arguments ('PT=' and 'SEVERITY=') so guess the sections simply
missing from the spec. I need that for stem support so please
give me a nudge when the event spec's done. :)
22:59 <+dgoulet> atagar: oh hmmm I'll fix that sorry
23:17 <+atagar> Thanks! Much appreciated. :)
```https://gitlab.torproject.org/tpo/core/torspec/-/issues/23Describe consensus digest calculation2022-02-21T19:12:25ZDamian JohnsonDescribe consensus digest calculationHi lovely network team folks. No doubt I'm being blind but I'm having difficulty figuring out how to calculate network status document digests.
During the voting period (minutes 55-60 of the hour) I fetched the detached signatures and u...Hi lovely network team folks. No doubt I'm being blind but I'm having difficulty figuring out how to calculate network status document digests.
During the voting period (minutes 55-60 of the hour) I fetched the detached signatures and upcoming consensus. The detached signatures cite the digest...
```
% curl http://128.31.0.39:9131/tor/status-vote/next/consensus-signatures > sigs
% curl http://128.31.0.39:9131/tor/status-vote/next/consensus > next_consensus
% grep consensus-digest sigs
consensus-digest 296BA01987256A1C8EFB20E17667152DCFA50755
```
But in trying hex encoded sha1s of various ranges of the consensus I'm having difficulty getting a value that matches that. No doubt I'm missing something but the spec is unhelpfully vague saying simply 'this is the digest' without citing a section describing how it's calculated...
https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n3309
It's probably buried in there somewhere but I've skimmed through the spec a few times and it's not jumping out at me. Mind clarifying in the spec how to calculate this?
Thanks!https://gitlab.torproject.org/tpo/core/torspec/-/issues/20Clarify the bandwidth part of dir-spec2022-02-21T19:12:25ZteorClarify the bandwidth part of dir-specPeople keep asking about the precise meaning of relay bandwidths. We should make the spec clearer:
https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n424
In particular:
* there is a separate limit on inbound and outbound traf...People keep asking about the precise meaning of relay bandwidths. We should make the spec clearer:
https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n424
In particular:
* there is a separate limit on inbound and outbound traffic
* traffic includes origin circuits and BEGINDIR requests
* let's check if traffic includes DirPort, I think it would have to
There may also be more feedback in legacy/trac#25854.
I'm tagging this fast-fix, because I can fix it fast, and it will save me time when I next explain it.