The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-11-23T15:34:15Zhttps://gitlab.torproject.org/tpo/web/support/-/issues/344Get rid of "Can I browse normal HTTPS sites with Tor?" support entry2023-11-23T15:34:15ZRoger DingledineGet rid of "Can I browse normal HTTPS sites with Tor?" support entryhttps://support.torproject.org/https/https-2/ is short and not all that enlightening.
```
The short answer is: Yes, you can browse normal HTTPS sites using Tor.
HTTPS Connections are used to secure communications over computer networks...https://support.torproject.org/https/https-2/ is short and not all that enlightening.
```
The short answer is: Yes, you can browse normal HTTPS sites using Tor.
HTTPS Connections are used to secure communications over computer networks. You can read
more about HTTPS here. Tor Browser's HTTPS-Only mode automatically switches thousands of
sites from unencrypted "HTTP" to more private "HTTPS".
```
I mean, of course you can browse https sites with Tor. In fact, that's basically all you should browse with Tor Browser.
What is a "normal" https site? Are we trying to mean "not .onion"?
What are we trying to answer here? Are we trying to teach people what https is?
I see that this entry maybe came to be based on common questions Gus got during trainings: https://github.com/torproject/support/pull/29#issuecomment-529112053
and it would be good to learn what the actual question was, to figure out if we already answer it elsewhere or what.https://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/issues/40040Get rid of gitweb reference2023-11-10T15:19:56ZGeorg KoppenGet rid of gitweb referenceGeorg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/network-health/metrics/tor-check/-/issues/40015Get rid of gitweb tor-check reference2023-11-13T15:56:22ZGeorg KoppenGet rid of gitweb tor-check referenceGeorg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/core/tor/-/issues/20014GETINFO version in torspec is inconsistent with the implementation2021-07-22T16:23:16ZteorGETINFO version in torspec is inconsistent with the implementationThe torspec description of GETINFO version is:
```
"version" -- The version of the server's software, including the name
of the software. (example: "Tor 0.0.9.4")
```
But tor responds:
```
GETINFO version
250-version=0.2.8.6 (...The torspec description of GETINFO version is:
```
"version" -- The version of the server's software, including the name
of the software. (example: "Tor 0.0.9.4")
```
But tor responds:
```
GETINFO version
250-version=0.2.8.6 (git-4d217548e3f05569)
250 OK
```
The "Tor " is missing from the response. We should remove it from the spec.Tor: 0.3.0.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/12833githax howto: where to send patches2021-07-22T16:25:47ZTracgithax howto: where to send patchesThe git howto at https://gitweb.torproject.org/githax.git didn't really specify where to send code patches, making it harder for new people (like me) to contribute code.
So I made a patch which says where to do this (trac.torproject.org...The git howto at https://gitweb.torproject.org/githax.git didn't really specify where to send code patches, making it harder for new people (like me) to contribute code.
So I made a patch which says where to do this (trac.torproject.org)
**Trac**:
**Username**: magnunorhttps://gitlab.torproject.org/tpo/onion-services/cebollitas/-/issues/10GitLab pages with l10n plugin2023-05-09T17:32:05ZSilvio RhattoGitLab pages with l10n pluginSetup GitLab pages with l10n plugin and using [onion-mkdocs](https://rhatto.pages.torproject.net/onion-mkdocs/).Setup GitLab pages with l10n plugin and using [onion-mkdocs](https://rhatto.pages.torproject.net/onion-mkdocs/).https://gitlab.torproject.org/tpo/core/arti/-/issues/508gitlab-pages is easy to forget to update, and interacts badly with coverage2022-12-13T20:44:03Ztrinity-1686agitlab-pages is easy to forget to update, and interacts badly with coveragethe [gitlab pages](https://tpo.pages.torproject.net/core/arti/) for Arti says it's still 0.3, but 0.4 is available.
Updating the `pages` branch would cause coverage report to disappear (and reappear on next scheduled CI job). I think t...the [gitlab pages](https://tpo.pages.torproject.net/core/arti/) for Arti says it's still 0.3, but 0.4 is available.
Updating the `pages` branch would cause coverage report to disappear (and reappear on next scheduled CI job). I think this branch should not exist, and the website should be directly on `main`. This would make the release process easier (only one branch to update), and would make the CI less strange in how deploying pages is done.https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40128Give standalone snowflakes guidance on how best to set up their nat2023-03-31T16:56:08ZRoger DingledineGive standalone snowflakes guidance on how best to set up their natAccording to our current broker stats (https://snowflake-broker.torproject.net/debug), we have
```
current snowflakes available: 3021
standalone proxies: 2589
browser proxies: 5
webext proxies: 250
unknown proxies: 177
NAT Types avai...According to our current broker stats (https://snowflake-broker.torproject.net/debug), we have
```
current snowflakes available: 3021
standalone proxies: 2589
browser proxies: 5
webext proxies: 250
unknown proxies: 177
NAT Types available:
restricted: 2512
unrestricted: 386
unknown: 123
```
i.e. most of the snowflakes that we're giving out seem to be standalone ones as opposed to browser extension ones, and also most of the ones we have available to us are behind restricted nat.
It seems to me that the standalone ones are probably in a better position to be behind the good kind of nat (or no nat at all). But does our docker image impose the bad kind of nat on them by default? How come so many standalone proxies are behind restricted nat?
More generally: is there useful guidance we can give people, on setting themselves up with the right kind of nat, presuming they're on a VPS or otherwise on a 'real' internet connection?shelikhooshelikhoohttps://gitlab.torproject.org/tpo/web/support/-/issues/162Glossary entry seems incomplete2022-07-01T04:42:25Zc1e0Glossary entry seems incompleteThe definition for [onion services](https://support.torproject.org/glossary/onion-services/) says:
> Onion services (formerly known as “hidden services”) are services (like websites) that are only accessible through the Tor network. Oni...The definition for [onion services](https://support.torproject.org/glossary/onion-services/) says:
> Onion services (formerly known as “hidden services”) are services (like websites) that are only accessible through the Tor network. Onion services offer advantages over ordinary services on the non-private web, including:
I believe there should be more sentences after the "including" word?https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40089Go over bridge descriptor spec and fix it up where needed2023-06-15T10:29:39ZGeorg KoppenGo over bridge descriptor spec and fix it up where neededWe removed contact information from our sanitization steps a while back in collector#20983 which is not visible on the bridge descriptor [spec](https://metrics.torproject.org/bridge-descriptors.html) yet. We should go over that spec and ...We removed contact information from our sanitization steps a while back in collector#20983 which is not visible on the bridge descriptor [spec](https://metrics.torproject.org/bridge-descriptors.html) yet. We should go over that spec and make sure everything is up-to-date.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/network-health/team/-/issues/100Go over metrics docs and replace references to gitweb with those to Gitlab an...2024-03-27T09:44:42ZGeorg KoppenGo over metrics docs and replace references to gitweb with those to Gitlab and move missing code if neededWe see Gitlab as the canonical place for metrics code nowadays, yet at least a bunch of docs still point to Gitweb (and it's not clear whether there are still code bases git.tpo-only).
We should go over our code and docs to make sure Gi...We see Gitlab as the canonical place for metrics code nowadays, yet at least a bunch of docs still point to Gitweb (and it's not clear whether there are still code bases git.tpo-only).
We should go over our code and docs to make sure Gitlab is indeed seen by all of that as the True Location.
/cc @hiro @irlGeorg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40018Go over metrics-lib website and fix content/outdated links2022-09-05T16:56:14ZGeorg KoppenGo over metrics-lib website and fix content/outdated linksI was reading up on `metrics-lib` and encountered e.g. a bunch of links we should update on https://metrics.torproject.org/metrics-lib.html (like releases still pointing to DescripTor (https://dist.torproject.org/descriptor/?C=M;O=D=) et...I was reading up on `metrics-lib` and encountered e.g. a bunch of links we should update on https://metrics.torproject.org/metrics-lib.html (like releases still pointing to DescripTor (https://dist.torproject.org/descriptor/?C=M;O=D=) etc.).https://gitlab.torproject.org/tpo/community/l10n/-/issues/40037Go through issues raised by translators in Transifex2021-08-05T08:31:28ZemmapeelGo through issues raised by translators in TransifexI started going through the issues translators raise in transifex, it takes some time, so I decided to open this ticket to account for the work.
Pending issues:
- [x] tpo:/about/history: "The network needed to be operated by entities wi...I started going through the issues translators raise in transifex, it takes some time, so I decided to open this ticket to account for the work.
Pending issues:
- [x] tpo:/about/history: "The network needed to be operated by entities with diverse interests and trust assumptions, and the software needed to be free and open to maximize transparency and separation." - [Separation? of what, concerns maybe? is not clear what does it mean regarding free and open software. Also, maybe is 'open source', not 'open'.](https://gitlab.torproject.org/tpo/web/tpo/-/issues/192)
- [ ] "In 2007, the organization began developing bridges to the Tor network to address censorship, such as the need to get around government firewalls, in order for its users to access the open web." - needs to be rephrased to be better understood:'... began developing bridges as an addition to the Tor network to provide solutions against censorship, such as government firewalls, to help users to maintain access to the open web.
- [x] Suggest feedback: change 'suggest feedback' on our lektor templates for 'give feedback' or 'leave a suggestion' (see in the bottom at for example: https://support.torproject.org/misc/bug-or-feedback/ )
- [x] in https://tb-manual.torproject.org/circumvention/ we say: `Or, if you have Tor Browser running, click on "Preferences" in the hamburger menu and then on "Tor" in the sidebar.` But there is no "Tor" sidebar in preferences.
- [ ] [main ticket](https://gitlab.torproject.org/tpo/web/manual/-/issues/94) On the manual, at https://tb-manual.torproject.org/mobile-tor/ , we say: When Tor Browser is running, you would see so in your phone's notification panel along with the button "NEW IDENTITY". But:
- to see the "new identity" button you must expand the notification.
- better: "in your device's notification panel"Sponsor 9 - Phase 5 - Usability and Community Intervention on Support for Democracy and Human Rightsemmapeelemmapeelhttps://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/40023Go through process of distributing private bridges2021-07-15T17:32:56ZPhilipp Winterphw@torproject.orgGo through process of distributing private bridgesOver at legacy/trac#31872, we created a process for distributing private bridges to NGOs:
https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam/NGOBridgeSupport
It's now time to go through this process with a non-tr...Over at legacy/trac#31872, we created a process for distributing private bridges to NGOs:
https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam/NGOBridgeSupport
It's now time to go through this process with a non-trivial number of censored users. Once we did, we need to document our experience and iteratively improve the process.Sponsor 30 - Objective 2.3GusGushttps://gitlab.torproject.org/tpo/web/manual/-/issues/142Google Play instructions need updating2023-07-03T14:48:49ZemmapeelGoogle Play instructions need updatingreported by translator olavinto, thanks!
The instructions for updating and uninstalling tor Browser with Google Play at
https://gitlab.torproject.org/tpo/web/manual/-/blob/main/content/mobile-tor/contents.lr
Need to be updated:
```...reported by translator olavinto, thanks!
The instructions for updating and uninstalling tor Browser with Google Play at
https://gitlab.torproject.org/tpo/web/manual/-/blob/main/content/mobile-tor/contents.lr
Need to be updated:
```
12:09 < olavinto[m]> * This phrase: "Tap on the hamburger menu next to the search bar and navigate to "My apps & games" >
"Installed". Select Tor Browser from the list of installed apps, then press the "Uninstall" button." has not been
exactly accurate for a while. The hamburger menu is still there although these days it's the logged in user's
icon and "My apps & games" has been "Manage apps and device" for a long time, and lastly, there is no "Installed"
12:09 < olavinto[m]> section under it anymore either but isntead there is a "Manage" (not the default tab, default is an overview) tab
and an "Installed" filtering option under that. Mainly that.
12:16 < olavinto[m]> Basically the whole section related to uninstalling the mobile app via Google Play now reads about like this in
Finnish: "Tap the user icon next to the search bar and select "Maintain apps and devices" > "Maintenance" from
the menu that opens. By default, the filtering options at the top are set to show only apps for which an update
is available. You can also search for Tor browser from the search field on the front page if you have a lot
12:16 < olavinto[m]> of applications on your device."
12:19 < olavinto[m]> s/By default, the filtering options at the top are set to show only apps for which an update is available.//
```championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/core/tor/-/issues/20986Gracefully handle build configurations on systems without AsciiDoc2022-02-07T19:38:32ZcypherpunksGracefully handle build configurations on systems without AsciiDocOn systems without AsciiDoc the build configuration aborts telling users to pass `--disable-asciidoc`. This requires users to restart the build configuration which is annoying.
Instead the build configuration should handle these cases g...On systems without AsciiDoc the build configuration aborts telling users to pass `--disable-asciidoc`. This requires users to restart the build configuration which is annoying.
Instead the build configuration should handle these cases gracefully and show a message without aborting the configuration. In these cases i would also show a less verbose message and change it to something similar to systems without Python, see https://gitweb.torproject.org/tor.git/tree/configure.ac?id=4098bfa26073551fe3f525ada7fc9079a49fd4bb#n218.https://gitlab.torproject.org/tpo/core/tor/-/issues/20637Grammar issue in HiddenServiceSingleHopMode documentation2021-07-22T16:22:54ZfkGrammar issue in HiddenServiceSingleHopMode documentationCurrently the tor man page contains the sentence:
```
Since a Single Onion is non-anonymous, you can not to run an
anonymous SOCKSPort on the same tor instance as a Single Onion service.
```
The attached patch is one way to fix it.Currently the tor man page contains the sentence:
```
Since a Single Onion is non-anonymous, you can not to run an
anonymous SOCKSPort on the same tor instance as a Single Onion service.
```
The attached patch is one way to fix it.Tor: 0.2.9.x-finalhttps://gitlab.torproject.org/tpo/community/hackweek/-/issues/35Hackweek 2023 documentation2023-11-30T17:35:12ZSilvio RhattoHackweek 2023 documentationDocument the 2023 Hackweek.Document the 2023 Hackweek.Hackweek 2023Silvio RhattoSilvio Rhatto2023-12-07https://gitlab.torproject.org/tpo/community/hackweek/-/issues/8Hackweek 2023: call for proposals message2023-11-30T16:17:38ZSilvio RhattoHackweek 2023: call for proposals messageSend the call for proposals email.Send the call for proposals email.Hackweek 2023Silvio RhattoSilvio Rhatto2023-08-30https://gitlab.torproject.org/tpo/community/hackweek/-/issues/6Hackweek 2023: call for proposals text2023-11-30T16:17:39ZSilvio RhattoHackweek 2023: call for proposals textCreate call for proposals text, inviting people to present proposals and join the Hackweek and including the following topics:
* [x] What:
* [x] Importance of documentation.
* [~] "How documentation affects me".
* [~] "How i can l...Create call for proposals text, inviting people to present proposals and join the Hackweek and including the following topics:
* [x] What:
* [x] Importance of documentation.
* [~] "How documentation affects me".
* [~] "How i can learn to help with this effort".
* [x] Why: goal of the Hackweek:
* [x] Explore how documentation is working or not in your projects.
* [x] Do problem-solving around documentation in the organization and projects we maintain.
* [x] Sharing the problems we have with documentation at Tor.
* [x] When: timeline:
* [x] Previous all hands meeting: people present the project they will work on.
* [x] During the Hackweek: people work on whatever they want related to
documentation (4-day Hackweek, from Mon to Thu).
* [x] Next all hands meeting: people present the project they worked on.
* [x] How: how the Hackweek is going to work (when, where):
* [x] People will add proposals to [Hackweek's issue tracker][] using an
[issue template][] and others can join to work together.
* [x] In order to join a proposal, subscribe yourself to it's ticket.
* [x] Accepting documentation in all formats, including videos/screencasts,
including things like "a video tutorial on my documentation best
practices".
* [x] References:
* [x] [Diátaxis](https://diataxis.fr/): The Grand Unified Theory of Documentation.
* [x] [How to pick up a project with an audit](https://bluesock.org/~willkg/blog/dev/auditing_projects.html)
[Hackweek's issue tracker]: https://gitlab.torproject.org/tpo/community/Hackweek/-/issues
[issue template]: tpo/community/hackweek#10Hackweek 2023Gabagaba@torproject.orgGabagaba@torproject.org2023-08-23