The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2022-02-07T19:39:17Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/18321Exclude our own vote from the consensus if we think our own vote is invalid2022-02-07T19:39:17ZteorExclude our own vote from the consensus if we think our own vote is invalidWe're creating a vote that is invalid, but try to make a consensus anyway like nothing's wrong. Then we fail doing that as described above.We're creating a vote that is invalid, but try to make a consensus anyway like nothing's wrong. Then we fail doing that as described above.https://gitlab.torproject.org/tpo/core/tor/-/issues/23168Guard sample calls relay descriptors a "consensus"2022-02-07T19:39:17ZteorGuard sample calls relay descriptors a "consensus"[info] router_load_routers_from_string: 96 elements to add
[info] sampled_guards_update_from_consensus: Updating sampled guard status based on received consensus.
The message should either say "received directory document(s)", or actual...[info] router_load_routers_from_string: 96 elements to add
[info] sampled_guards_update_from_consensus: Updating sampled guard status based on received consensus.
The message should either say "received directory document(s)", or actually describe the directory document it just received.https://gitlab.torproject.org/tpo/core/tor/-/issues/2983Errant circuit creation beyond MAPADDRESS validity2022-02-07T19:40:54ZgrarpampErrant circuit creation beyond MAPADDRESS validityI think I found something strange. Consider the following shell
script.
for exit in list_of_exits ; do
mapaddress example.com=example.com.$exit.exit [1]
Fire off ten to twenty background processes in parallel that try
to connect to...I think I found something strange. Consider the following shell
script.
for exit in list_of_exits ; do
mapaddress example.com=example.com.$exit.exit [1]
Fire off ten to twenty background processes in parallel that try
to connect to example.com. Depending on timing and other issues,
some may succeed, some may fail, some may be waiting their timeout
retry period due to failure to connect to example.com the first
time, etc. Think wget here.
wait - 'wait' them in the shell till they all exit.
mapaddress example.com=example.com [3]
mapaddress example.com.$exit.exit=example.com.$exit.exit [2]
getinfo address-mappings/all
done
[2] Now this map effectively clears the dynamically made map (from
[1]) to the default (no) mapping. And the getinfo confirms it is
gone. The shell 'wait' ensures that the spawned processes are all
gone and thus do not remain to make further use of the map in [1].
The bug is... sometimes (while for'ing through the long list of
exits), at the end of the next iteration of the loop (and beyond,
until the old entry expires), getinfo will show a dynamic entry for
the previous exit. Of the form:
example.com.<exit>.exit <it's IP address>.<exit>.exit "2011-04-xx xx:xx:xx"
My guess is that the processes put in a request for a circuit (by
simply trying to connect). But that [2] doesn't kill that request
within Tor, it only removes any dynamic map that currently exists.
I subsequently tested by adding [3], it had no effect on this issue.
I believe both [2] and [3] should kill any pending requests for
their respective, formerly mapped, entities.
Also, I see this every once in a while, no real hypothesis other
than something similar is going on:
example.com <it's IP address> "2011-04-xx xx:xx:xx"https://gitlab.torproject.org/tpo/core/tor/-/issues/3145excludeexitnodes by ip misleading when exit relay uses outboundbindaddress2022-02-07T19:41:18ZRoger Dingledineexcludeexitnodes by ip misleading when exit relay uses outboundbindaddressIn legacy/trac#3143 we have a user who tried to set ExcludeExitNodes with an IP address based on the address of his Tor traffic. It didn't work, because the exit relay in question exits from a different IP address than it advertises in i...In legacy/trac#3143 we have a user who tried to set ExcludeExitNodes with an IP address based on the address of his Tor traffic. It didn't work, because the exit relay in question exits from a different IP address than it advertises in its descriptor.
My first answer was "well, you should be excluding exit nodes by fingerprint". But that isn't a very satisfactory answer.
We could have the descriptors (and microdescriptors, ugh) or the consensus mention alternate IPs for this purpose.
It was easy for me to look up because moria1's cached-descriptor file says
```
@uploaded-at 2011-05-09 17:38:43
@source "66.249.9.107"
router ecksnet 66.249.9.183 80 0 0
```
but that isn't going to be so easy for others.
There's also the tor bulk exit lists:
https://metrics.torproject.org/data.html#exitlist
which have this clause for the relay in question:
```
ExitNode 07E9456ED300CABCE2549119FE5B3CC27DA55585
Published 2011-05-10 11:39:28
LastStatus 2011-05-11 06:04:20
ExitAddress 66.249.9.107 2011-05-10 12:33:34
```
but that's not exactly easier for users to know about or use either.https://gitlab.torproject.org/tpo/web/community/-/issues/54Link to Developer portal in Community Landing page2022-02-07T20:44:33ZPili GuerraLink to Developer portal in Community Landing page### Problem to solve
How do we make developers feel part of the community also?
### Intended users
Developers
### Further details
On the landing page, we may want to have a card for developers that will eventually point to the newl...### Problem to solve
How do we make developers feel part of the community also?
### Intended users
Developers
### Further details
On the landing page, we may want to have a card for developers that will eventually point to the newly created developer portal. To begin with, we could start off by pointing this to the archive
Thanks to gaba for proposing this.
### Proposal
1. Add a card for developers to the community portal
2. Create some artwork for the developers
3. Point the card to the website archive
4. When the developer portal is live, point the card to the developer portalCommunity Portal: Public Launchhttps://gitlab.torproject.org/tpo/web/community/-/issues/48[Content] Add Resources for Trainers under media.tpo2022-02-07T20:44:33ZPili Guerra[Content] Add Resources for Trainers under media.tpoOnce media.tpo has been cleaned up and re-structured, add training resources thereOnce media.tpo has been cleaned up and re-structured, add training resources thereCommunity Portal: Public Launch2019-12-31https://gitlab.torproject.org/tpo/web/community/-/issues/16[Content] New Trainer2022-02-07T20:44:33ZPili Guerra[Content] New TrainerInfo for trainersInfo for trainersTraining Section Complete2019-05-31https://gitlab.torproject.org/tpo/ux/research/-/issues/73Design graphic to support call for participation in Brazil & Mexico2022-02-07T22:44:57ZNahDesign graphic to support call for participation in Brazil & MexicoWe are organizing a training cycle with The Guardian Project and Tails in March. The training agenda will present an Introduction to Tor Browser Desktop, Tor Browser Android and Onion Browser, Orbot and Tails in different dates. It will ...We are organizing a training cycle with The Guardian Project and Tails in March. The training agenda will present an Introduction to Tor Browser Desktop, Tor Browser Android and Onion Browser, Orbot and Tails in different dates. It will happen in Brazil and Mexico, both remotely, for participants that apply for the Call for Participation (CFP).
The CFP will be shared online through communication channels (such as Twitter) during February. We need a visual art to go with it, to make it more attractive to recruit participants.
Some elements to this visual art:
- Tor, Tails, Orbot, Onion Browser icons;
- Usability and Training illustration
- Privacy /Anonymity illustration
It doesn't need all these elements together, this is just a suggestion.Sponsor 30 - Objective 3.4nicobnicob2022-02-07https://gitlab.torproject.org/tpo/anti-censorship/bridge-port-scan/-/issues/5missing instructions on how to install sass2022-02-08T00:13:10Zmeskiomeskio@torproject.orgmissing instructions on how to install sassThe readme lists the dependencies that you need to install (like lektor or python3), but doesn't mention sass which seems to be needed to [build the templates](https://gitlab.torproject.org/tpo/anti-censorship/bridge-port-scan/-/blob/mai...The readme lists the dependencies that you need to install (like lektor or python3), but doesn't mention sass which seems to be needed to [build the templates](https://gitlab.torproject.org/tpo/anti-censorship/bridge-port-scan/-/blob/main/build.sh#L21). I'm not sure what is the preferred method to install it, I don't find it as a debian package, do you install it with npm?https://gitlab.torproject.org/tpo/anti-censorship/bridge-port-scan/-/issues/3Give a better error message when the user asks us to scan 192.168.x.y2022-02-08T00:34:49ZRoger DingledineGive a better error message when the user asks us to scan 192.168.x.yWe have a user setting up a bridge with port forwarding, and they were using the 'scan' tool to see if it's reachable, but it was saying that it's unreachable, with reason timeout -- and it turns out they were asking it about 192.168.1.5...We have a user setting up a bridge with port forwarding, and they were using the 'scan' tool to see if it's reachable, but it was saying that it's unreachable, with reason timeout -- and it turns out they were asking it about 192.168.1.53.
We should intercept requests to scan rfc1918 netblocks, and give users more actionable feedback, e.g. pointing them to something that teaches them about private addresses and why they need to be testing their *external* address here.https://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/32Remove old objects by removing the objects they're related to2022-02-08T08:59:00ZjugaRemove old objects by removing the objects they're related toonbasca: 1.0jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/25Order bwlines by bw2022-02-08T08:59:00ZjugaOrder bwlines by bwonbasca: 1.0jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/24Split torcontrol methods to measure into other file2022-02-08T08:59:00ZjugaSplit torcontrol methods to measure into other fileonbasca: 1.0jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/12Finish separating measurements code from torcontrol2022-02-08T08:59:00ZjugaFinish separating measurements code from torcontrolonbasca: 1.0jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/45Add under_min_report KeyValue2022-02-08T08:59:00ZjugaAdd under_min_report KeyValueonbasca: 1.0jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/11Write about why sbws2/onbasca2022-02-08T08:59:00ZjugaWrite about why sbws2/onbascaonbasca: 1.0jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/39Update Web servers from configuration when the scanner is started2022-02-08T08:59:00ZjugaUpdate Web servers from configuration when the scanner is startedonbasca: 1.0jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/40Remove KeyValues from the RelayLines when there aren't successful measurements2022-02-08T08:59:00ZjugaRemove KeyValues from the RelayLines when there aren't successful measurements********onbasca: 1.0jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/29Add s61 label to the issues that has been solved as part of it2022-02-08T08:59:00ZjugaAdd s61 label to the issues that has been solved as part of itonbasca: 1.0jugajugahttps://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/30Solve recursion when deleting old consensuses2022-02-08T08:59:01ZjugaSolve recursion when deleting old consensusesonbasca: 1.0jugajuga