The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2021-08-23T16:29:33Zhttps://gitlab.torproject.org/tpo/web/support/-/issues/100Glossary: add term 'hamburguer menu'2021-08-23T16:29:33ZemmapeelGlossary: add term 'hamburguer menu'add the term, preferably with a link to some external reference, a little image explaining what it is, etc.
how to add a new word to glossary: https://gitlab.torproject.org/torproject/web/wiki/-/blob/master/Add-glossary-term.mdadd the term, preferably with a link to some external reference, a little image explaining what it is, etc.
how to add a new word to glossary: https://gitlab.torproject.org/torproject/web/wiki/-/blob/master/Add-glossary-term.mdhttps://gitlab.torproject.org/tpo/core/tor/-/issues/33779Fix incorrect PublishHidServDescriptors value in logs2021-06-23T17:22:41ZteorFix incorrect PublishHidServDescriptors value in logsThis code should say:
"PublishHidServDescriptors is set to 0."
But it says:
```
/* Let's avoid doing that if tor is configured to not publish. */
if (!get_options()->PublishHidServDescriptors) {
log_info(LD_REND, "Service %s not...This code should say:
"PublishHidServDescriptors is set to 0."
But it says:
```
/* Let's avoid doing that if tor is configured to not publish. */
if (!get_options()->PublishHidServDescriptors) {
log_info(LD_REND, "Service %s not publishing descriptor. "
"PublishHidServDescriptors is set to 1.",
safe_str_client(service->onion_address));
goto end;
}
```
I'll leave it to dgoulet and asn to fix, and decide how far it needs to be backported.Tor: 0.4.4.x-finalDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/33742Add information about design paper and anonbib inside README.1st2021-06-23T11:55:13ZGhost UserAdd information about design paper and anonbib inside README.1stAs mentioned under legacy/trac#33688 (comment 9) some old "TODO" items were removed from `doc/HACKING/README.1st.md` file.
Link and description should be added for:
- design paper,
- anonbib.As mentioned under legacy/trac#33688 (comment 9) some old "TODO" items were removed from `doc/HACKING/README.1st.md` file.
Link and description should be added for:
- design paper,
- anonbib.https://gitlab.torproject.org/tpo/core/tor/-/issues/33741Format code blocks inside markdown files (documentation)2021-07-22T16:18:20ZGhost UserFormat code blocks inside markdown files (documentation)There are issues with code blocks inside some *.md files (some files use code blocks syntax, some do not). First of all, it's not consistent but what's really bad is when *.md file is being displayed incorrectly. You can find an example ...There are issues with code blocks inside some *.md files (some files use code blocks syntax, some do not). First of all, it's not consistent but what's really bad is when *.md file is being displayed incorrectly. You can find an example of what I'm saying in CodingStandards.md under How we log changes section.
​https://github.com/torproject/tor/blob/master/doc/HACKING/CodingStandards.md#how-we-log-changes
Part of the git log output is still displayed as a regular text rather than a formatted code block.
Goal of this ticket is to go through all *.md files under `doc` and `doc/HACKING` directories and format code snippets accordingly.
```
```c
// code snippet
// written in
// C language
```
```
```
```bash
// command to be run
// inside bash
```
```
This should fix the issues described above and enable syntax highlighting on supported websites and editors.Tor: unspecifiedGuinnessGuinnesshttps://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/33709BridgeDB's deployment scripts are broken2020-10-29T20:26:03ZPhilipp Winterphw@torproject.orgBridgeDB's deployment scripts are brokenWhen running `~/bridgedb-admin/bin/deploy` on polyanthum, I suddenly get:
```
[...]
"$BIN_DIR"/run-bridgedb
+ /srv/bridges.torproject.org/bin/run-bridgedb
Starting BridgeDB... [OK]
exit $?
+ exit 0
(bridgedb) [21:23:16] bridg...When running `~/bridgedb-admin/bin/deploy` on polyanthum, I suddenly get:
```
[...]
"$BIN_DIR"/run-bridgedb
+ /srv/bridges.torproject.org/bin/run-bridgedb
Starting BridgeDB... [OK]
exit $?
+ exit 0
(bridgedb) [21:23:16] bridgedb@polyanthum ~$ Traceback (most recent call last):
File "/home/bridgedb/virtualenvs/bridgedb/bin/bridgedb", line 4, in <module>
__import__('pkg_resources').run_script('bridgedb==0.9.4+0.g9a7ae57c.dirty', 'bridgedb')
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/pkg_resources/__init__.py", line 667, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/pkg_resources/__init__.py", line 1455, in run_script
.format(**locals()),
pkg_resources.ResolutionError: Script 'scripts/bridgedb' not found in metadata at '/srv/bridges.torproject.org/home/bridgedb/bridgedb.egg-info'
```
...and BridgeDB won't start. This may have something to do with the `setuptools` package.Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/91Update link in "Exit Policies" question to new abuse faq location2021-08-23T16:29:33ZGusUpdate link in "Exit Policies" question to new abuse faq locationIn this question https://support.torproject.org/operators/exit-policies/ we need to replace this URL url:
https://2019.www.torproject.org/docs/faq-abuse.html.en#TypicalAbuses
to
https://support.torproject.org/abuse/exit-relay-expectations/In this question https://support.torproject.org/operators/exit-policies/ we need to replace this URL url:
https://2019.www.torproject.org/docs/faq-abuse.html.en#TypicalAbuses
to
https://support.torproject.org/abuse/exit-relay-expectations/https://gitlab.torproject.org/tpo/core/tor/-/issues/33670Fix erroneous spaces in circuitmux_ewma.c2020-06-27T13:48:01ZNeel Chauhanneel@neelc.orgFix erroneous spaces in circuitmux_ewma.cNeel Chauhanneel@neelc.orgNeel Chauhanneel@neelc.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/33632List ed25519 fingerprints on the command line2021-04-18T13:55:23ZteorList ed25519 fingerprints on the command lineFor RSA keys, tor has `tor --list-fingerprint`.
We could add a feature to tor so it accepts a key type argument:
* `tor --list-fingerprint rsa`
* `tor --list-fingerprint ed25519`
And defaults to RSA (for now).
Related to legacy/trac#30...For RSA keys, tor has `tor --list-fingerprint`.
We could add a feature to tor so it accepts a key type argument:
* `tor --list-fingerprint rsa`
* `tor --list-fingerprint ed25519`
And defaults to RSA (for now).
Related to legacy/trac#30642, which adds an `ed25519-fingerprint` file.https://gitlab.torproject.org/tpo/web/lego/-/issues/7We need robots.txt in all our website2022-07-01T05:22:37ZHiroWe need robots.txt in all our websiteSee: https://trac.torproject.org/projects/tor/ticket/33496See: https://trac.torproject.org/projects/tor/ticket/33496https://gitlab.torproject.org/tpo/core/chutney/-/issues/33609Check that onion services have successfully posted descriptors before verifying2020-07-07T15:12:56ZteorCheck that onion services have successfully posted descriptors before verifyingBefore verifying, chutney checks that:
* each relay descriptor is cached at each node
* each relay is in a consensus, cached at each node
* each relay is in a microdesc consensus, cached at each node
* each bridge descriptor is cached at...Before verifying, chutney checks that:
* each relay descriptor is cached at each node
* each relay is in a consensus, cached at each node
* each relay is in a microdesc consensus, cached at each node
* each bridge descriptor is cached at each bridge client
We have other tickets for checking:
* microdescriptors
* cached bridge descriptors at the bridge authority
* the bridge networkstatus
That just leaves onion services.
Onion services are tricky, because they post to some HSDirs in the network, but not all. And those HSDirs don't cache the onion service descriptors in a file.
So here is one possible design for this feature:
* check each onion service log for a successful descriptor post to at least one HSDir
* check v2 and v3 onion services
* call it an extra 200% "bootstrap" stage (because it's a sender log check, not a receiver cached file check)
* require 200% bootstrap for onion servicesNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33595Stop waiting for unchecked directory info2020-06-27T13:18:32ZteorStop waiting for unchecked directory infoOnce we've fixed legacy/trac#33428 (microdescs), legacy/trac#33582 (bridges), and legacy/trac#33609 (onion services), we might be able to remove WAIT_FOR_UNCHECKED_DIR_INFO in chutney's TorNet.py.
But we might still need to wait for:
* ...Once we've fixed legacy/trac#33428 (microdescs), legacy/trac#33582 (bridges), and legacy/trac#33609 (onion services), we might be able to remove WAIT_FOR_UNCHECKED_DIR_INFO in chutney's TorNet.py.
But we might still need to wait for:
* internal tor state changes, in response to downloading descriptors.
So we will need to make this change, then test it on Tor 0.3.5 and master.https://gitlab.torproject.org/tpo/core/tor/-/issues/33555Space out the line.key/line.value in test_policy_summary_helper_family_flags()2020-06-27T13:48:05ZNeel Chauhanneel@neelc.orgSpace out the line.key/line.value in test_policy_summary_helper_family_flags()Tor: 0.4.4.x-finalNeel Chauhanneel@neelc.orgNeel Chauhanneel@neelc.orghttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/33472Document that bwauths should checkout stable versions when installing sbws fr...2020-07-14T16:44:07ZjugaDocument that bwauths should checkout stable versions when installing sbws from giti think that if some bwauths are installing sbws from git, they should checkout a tag or a bugfix branch. We might want to have a bwauth to run a development branch, but it should be only one.i think that if some bwauths are installing sbws from git, they should checkout a tag or a bugfix branch. We might want to have a bwauth to run a development branch, but it should be only one.sbws: 1.1.x-finaljugajugahttps://gitlab.torproject.org/tpo/core/tor/-/issues/33463Correct spacing in dns_launch_correctness_checks()2020-06-27T13:48:07ZNeel Chauhanneel@neelc.orgCorrect spacing in dns_launch_correctness_checks()Tor: 0.4.4.x-finalNeel Chauhanneel@neelc.orgNeel Chauhanneel@neelc.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/33371Build only with required libevent2 libraries2023-09-15T11:40:49ZNick MathewsonBuild only with required libevent2 librariesWe should only need libevent_core and libevent_extra.We should only need libevent_core and libevent_extra.https://gitlab.torproject.org/tpo/core/tor/-/issues/33339Add script to check ordering of options in manpage2021-07-22T16:18:20ZTaylor YuAdd script to check ordering of options in manpageAdd a script to check the ordering of option names within a manpage section.
This will be an initial version that doesn't restrict section names and doesn't recognize pragma comments that mark intentionally out-of-order option names.
l...Add a script to check the ordering of option names within a manpage section.
This will be an initial version that doesn't restrict section names and doesn't recognize pragma comments that mark intentionally out-of-order option names.
legacy/trac#32621 will contain a more fully-functional script suitable for automation.Tor: 0.4.3.x-finalTaylor YuTaylor Yuhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33298HTTP onion sites do not give a popup warning when submitting form data to non...2023-06-11T04:21:10ZrichardHTTP onion sites do not give a popup warning when submitting form data to non-onion HTTP sitesIn vanilla firefox, HTTPS site with a form that submits to an HTTP site will put up a pop-up box warning the user they are about to send their data unencrypted across the network. Tor Browser follows this behaviour, but it also needs to ...In vanilla firefox, HTTPS site with a form that submits to an HTTP site will put up a pop-up box warning the user they are about to send their data unencrypted across the network. Tor Browser follows this behaviour, but it also needs to do so when submitting data from an HTTP onionsite to a vanilla HTTP site.ma1ma1https://gitlab.torproject.org/tpo/core/tor/-/issues/33275Tor Manual: Alphabetize Remaining Tor Manual2021-07-22T16:18:20ZTracTor Manual: Alphabetize Remaining Tor ManualAlphabetically sort the options in the following sections:
- DENIAL OF SERVICE MITIGATION OPTIONS
- DIRECTORY AUTHORITY SERVER OPTIONS
- HIDDEN SERVICE OPTIONS
- TESTING NETWORK OPTIONS
**Trac**:
**Username**: swatiAlphabetically sort the options in the following sections:
- DENIAL OF SERVICE MITIGATION OPTIONS
- DIRECTORY AUTHORITY SERVER OPTIONS
- HIDDEN SERVICE OPTIONS
- TESTING NETWORK OPTIONS
**Trac**:
**Username**: swatiTor: 0.4.4.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/33188Tor Manual: Alphabetize Server and Directory Server Options2021-07-22T16:18:20ZTracTor Manual: Alphabetize Server and Directory Server OptionsAlphabetize options in the Server Options and Directory Server Options
**Trac**:
**Username**: swatiAlphabetize options in the Server Options and Directory Server Options
**Trac**:
**Username**: swatihttps://gitlab.torproject.org/tpo/web/tpo/-/issues/57add mastodon link to https://www.torproject.org/contact/2021-08-23T16:33:41Zemmapeeladd mastodon link to https://www.torproject.org/contact/reported by kushal:
we should update our contact page with the very active mastodon accountreported by kushal:
we should update our contact page with the very active mastodon account