The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2020-07-23T18:07:33Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/7360Document process of collection and extraction, formatting, etc.2020-07-23T18:07:33ZRob JansenDocument process of collection and extraction, formatting, etc.Self explanatory. People need to know how to extract the statistics and what they're extracting to be most useful.Self explanatory. People need to know how to extract the statistics and what they're extracting to be most useful.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40213Document procedure for repairing broken https-e idb2022-07-09T19:25:15ZMatthew FinkelDocument procedure for repairing broken https-e idbSee https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests/71#note_2714402See https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests/71#note_2714402Tor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/core/tor/-/issues/7982document path bias torrc options in the code2020-06-27T14:04:56ZRoger Dingledinedocument path bias torrc options in the code```
/**
* Parameters for path-bias detection.
* @{
*/
int PathBiasCircThreshold;
double PathBiasNoticeRate;
double PathBiasDisableRate;
int PathBiasScaleThreshold;
int PathBiasScaleFactor;
/** @} */
```
What are e...```
/**
* Parameters for path-bias detection.
* @{
*/
int PathBiasCircThreshold;
double PathBiasNoticeRate;
double PathBiasDisableRate;
int PathBiasScaleThreshold;
int PathBiasScaleFactor;
/** @} */
```
What are each of these? How do they differ? Is DisableRate the one about dropping guards? This doxygen comment doesn't help me.Tor: 0.2.4.x-finalAndrea ShepardAndrea Shepardhttps://gitlab.torproject.org/tpo/core/tor/-/issues/32971Document OwningControllerProcess time interval2021-07-22T16:18:20ZteorDocument OwningControllerProcess time intervalTor checks for its owning controller process every 15 seconds:
https://github.com/torproject/tor/blob/4f02812242d1fd90d859eb98ac3fb1ed182f18cf/src/lib/evloop/procmon.c#L168
We should document this interval in the man page.Tor checks for its owning controller process every 15 seconds:
https://github.com/torproject/tor/blob/4f02812242d1fd90d859eb98ac3fb1ed182f18cf/src/lib/evloop/procmon.c#L168
We should document this interval in the man page.Tor: 0.4.3.x-finalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/25628Document our Rust coding standards for error/failure types2021-07-22T16:20:50ZIsis LovecruftDocument our Rust coding standards for error/failure typesEvery crate which returns `Result<T, E>`s or `Option<T>` anywhere in its public interface should have an `errors.rs` module containing error types which implement either `Display` or `Debug`. See the `errors.rs` addition to the `protover...Every crate which returns `Result<T, E>`s or `Option<T>` anywhere in its public interface should have an `errors.rs` module containing error types which implement either `Display` or `Debug`. See the `errors.rs` addition to the `protover` crate from legacy/trac#24031 for an example.
In the future, when failure is 1.0.0, we should also require `::failure::Fail` for making errors easier to work with between crates.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/community/outreach/-/issues/20928Document our privacy-preserving webserver log setup for the world2022-11-11T12:28:56ZRoger DingledineDocument our privacy-preserving webserver log setup for the worldWe use a novel log format for our webservers, which makes sure we don't collect the IP addresses of our visitors, and doesn't record the precise timestamp of the visits, yet still produces a format compatible with various log parsing too...We use a novel log format for our webservers, which makes sure we don't collect the IP addresses of our visitors, and doesn't record the precise timestamp of the visits, yet still produces a format compatible with various log parsing tools.
Everybody in the world should be doing this.
We should document what we do and how and why, and tell the world so everybody else can do it too.
Apparently Debian uses the same approach we do, so we have some adoption already, but much more remains!
See
http://seclists.org/nmap-announce/2004/16
for some of our original motivation.
And see
http://lists.spi-inc.org/pipermail/spi-general/2016-December/003645.html
for a summary of what we do currently.
We should also invite/encourage people to find bugs in our set-up. It can always get better!
And lastly, a blog post like this will be really useful to point to when we start doing analysis and graphs and metrics and stuff.https://gitlab.torproject.org/tpo/core/tor/-/issues/25310Document our policy for Rust dependencies2021-07-22T16:21:38ZIsis LovecruftDocument our policy for Rust dependenciesWe should document what our (experimental, subject to change) policies are w.r.t. new Rust dependencies in tor, somewhere in the `doc/HACKING/` directory.We should document what our (experimental, subject to change) policies are w.r.t. new Rust dependencies in tor, somewhere in the `doc/HACKING/` directory.Tor: 0.3.4.x-finalhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40979document our fastly/CDN setup2022-11-30T19:55:45Zanarcatdocument our fastly/CDN setupso we have a CDN we use here, and it's not really documented. we have fairly good docs on the ~"static-component" system, but nothing on ~Fastly. we didn't even have a tag for it until #40978 was filed (and i made it).
so we should docu...so we have a CDN we use here, and it's not really documented. we have fairly good docs on the ~"static-component" system, but nothing on ~Fastly. we didn't even have a tag for it until #40978 was filed (and i made it).
so we should document:
* [ ] what we use fastly for
* [ ] how it's configured (e.g. `cdn-config-fastly.git`, `./tor-puppet/modules/roles/files/puppetmaster/update-fastly-ips`, static-component yaml file, probably more)
* [ ] what talks to it and why not everything is on there
* [ ] what our limits are
* [ ] contact information
* [ ] password management
basically make a full service audit.anarcatanarcathttps://gitlab.torproject.org/tpo/core/tor/-/issues/14742Document or remove the --digests option to tor2020-06-27T14:01:49ZNick MathewsonDocument or remove the --digests option to torIf nobody's using it, we should throw it out. If it's useful, we should document it.If nobody's using it, we should throw it out. If it's useful, we should document it.Tor: 0.2.7.x-finalhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41194document OpenPGP and yubikey operation (and replace my yubikey)2023-07-11T14:46:13Zanarcatdocument OpenPGP and yubikey operation (and replace my yubikey)i've been working on a yubikey + openpgp guide because I want to replace my old Yubikey NEO with a fresh new YK 5 instead. i'll document my work for everyone here to see (scary, no?).
this is already happening in `howto/yubikey.md` in t...i've been working on a yubikey + openpgp guide because I want to replace my old Yubikey NEO with a fresh new YK 5 instead. i'll document my work for everyone here to see (scary, no?).
this is already happening in `howto/yubikey.md` in the wiki, this ticket is merely to keep track of progress and not let my dashboard be blank as that would be a lie.
- [x] write procedure
- [x] test procedure
- [x] verify procedure, fixing all TODO items
- [x] decide where to put the backup (!)
- [x] re-encrypt password-manager
- [x] publish new key
- [x] decide what to do with old encryption key?
- [x] share a backup with a SSSS schemeanarcatanarcathttps://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/24420Document Onionoo protocol version 4.42020-06-27T14:26:00ZKarsten LoesingDocument Onionoo protocol version 4.4The current Onionoo protocol version is 4.3, but we started merging changes for the next protocol version 4.4. Let's collect these changes here, so that we can update the specification page once we're releasing 4.4:
https://gitweb.torpr...The current Onionoo protocol version is 4.3, but we started merging changes for the next protocol version 4.4. Let's collect these changes here, so that we can update the specification page once we're releasing 4.4:
https://gitweb.torproject.org/karsten/metrics-web.git/commit/?h=tasks-22488-23962-21827-23544&id=b01aaf6a5efb0e7198c5d27baddd80b8b68be19bOnionoo-1.8.0https://gitlab.torproject.org/tpo/onion-services/onion-launchpad/-/issues/65Document Onion Launchpad threat model2022-12-12T16:59:59ZSilvio RhattoDocument Onion Launchpad threat modelThe Onion Launchpad threat model [was drafted](https://gitlab.torproject.org/tpo/onion-services/onion-launchpad/-/issues/39#note_2854486) and needs to be included into the documentation.The Onion Launchpad threat model [was drafted](https://gitlab.torproject.org/tpo/onion-services/onion-launchpad/-/issues/39#note_2854486) and needs to be included into the documentation.Sponsor 123: Tor Secure Access Package for USAGM [First Phase]Silvio RhattoSilvio Rhattohttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29292Document number of threads configuration depending on the machine available b...2022-02-17T19:58:39ZjugaDocument number of threads configuration depending on the machine available bandwidthFor instance, how many threads can we have when the machine available bandwidth is 100Mbps or 1Gbps.
Based on what we talked in https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetworkTeam/Notes/SBWSRoadmap#QuestionsFor instance, how many threads can we have when the machine available bandwidth is 100Mbps or 1Gbps.
Based on what we talked in https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsNetworkTeam/Notes/SBWSRoadmap#Questionssbws: unspecifiedhttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29723Document next steps and/or tickets remaining2020-06-27T13:41:18ZjugaDocument next steps and/or tickets remainingSince soon i'll have less time to work on this, gaba proposed i create a document explaining which would be the next steps.
This would be basically the open tickets, but probably it requires some other explanation and/or (re-)assign mile...Since soon i'll have less time to work on this, gaba proposed i create a document explaining which would be the next steps.
This would be basically the open tickets, but probably it requires some other explanation and/or (re-)assign milestones to tickets, close some or open others.sbws: 1.1.x-finaljugajugahttps://gitlab.torproject.org/tpo/network-health/sbws/-/issues/29752Document new sbws Gitlab labels2022-02-18T20:48:05ZjugaDocument new sbws Gitlab labelssbws: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/19300Document miscellaneous things in src/common in tor-guts2021-07-22T16:23:16ZNick MathewsonDocument miscellaneous things in src/common in tor-gutsThis is the grab-bag of stuff without other tickets: pubsub, timers, di_ops, torgzip, torlog, util_bug, workqueue.This is the grab-bag of stuff without other tickets: pubsub, timers, di_ops, torgzip, torlog, util_bug, workqueue.Tor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/27677document minimum required python versions2021-07-22T16:20:36ZTaylor Yudocument minimum required python versionsIt looks like at least sometimes we end up using python constructs that require python >=2.7 or >= 3.1. (See legacy/trac#27675 for an example.) We should document this somewhere, possibly in doc/HACKING.It looks like at least sometimes we end up using python constructs that require python >=2.7 or >= 3.1. (See legacy/trac#27675 for an example.) We should document this somewhere, possibly in doc/HACKING.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/network-health/team/-/issues/254Document metrics dashboards in our wiki2022-09-27T14:23:09ZGeorg KoppenDocument metrics dashboards in our wikiThanks mostly to @hiro's work we have a bunch of dashboards with useful data now. However, given that a lot of them have grown out of experimentation with the tooling and data there is a certain amount of "mushrooming" visible, which mak...Thanks mostly to @hiro's work we have a bunch of dashboards with useful data now. However, given that a lot of them have grown out of experimentation with the tooling and data there is a certain amount of "mushrooming" visible, which makes it hard to keep track of the important and useful dashboards. (Right now, I am fighting with a bunch of bookmarks in my browser for that, often forgetting where and whether we have data X visualized)
We should create something like metrics/dashboards in our wiki where we list our useful (could be experimental as well!) dashboards, explaining what they provide with links to them and to the scripts "sustaining" those dashboards.HiroHirohttps://gitlab.torproject.org/tpo/core/tor/-/issues/19299Document memory-related parts of src/common in tor-guts2021-07-22T16:23:16ZNick MathewsonDocument memory-related parts of src/common in tor-gutsTor: 0.2.9.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/30349Document member-hiding conventions for structs2022-06-17T14:06:50ZTaylor YuDocument member-hiding conventions for structsWe should document whatever conventions we choose for hiding struct members, probably in doc/HACKING. Also we should make tools for searching for violations, e.g., code that directly accesses private members without using the appropriate...We should document whatever conventions we choose for hiding struct members, probably in doc/HACKING. Also we should make tools for searching for violations, e.g., code that directly accesses private members without using the appropriate macros. (A fairly simple Coccinelle script should work for this.)