Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:39:50Zhttps://gitlab.torproject.org/legacy/trac/-/issues/29897Refactor handle_get_next_bandwidth() to use connection_dir_buf_add()2020-06-13T15:39:50ZteorRefactor handle_get_next_bandwidth() to use connection_dir_buf_add()After #21377 merges, we want to refactor handle_get_next_bandwidth() to use connection_dir_buf_add().
If we backport this refactor to 0.4.0 or earlier, we'll also need #29896 for the connection_dir_buf_add() backport.After #21377 merges, we want to refactor handle_get_next_bandwidth() to use connection_dir_buf_add().
If we backport this refactor to 0.4.0 or earlier, we'll also need #29896 for the connection_dir_buf_add() backport.Tor: 0.4.0.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/24805Update fallback whitelist in late 20182020-06-13T15:19:52ZteorUpdate fallback whitelist in late 2018We need to update the list using:
* operator emails from 2018
* the opt-in process in #24804
* ~~running the script, finding change warnings, contacting operators, and updating their details~~ we'll do #24838 insteadWe need to update the list using:
* operator emails from 2018
* the opt-in process in #24804
* ~~running the script, finding change warnings, contacting operators, and updating their details~~ we'll do #24838 insteadTor: 0.4.0.x-finalColin ChildsColin Childshttps://gitlab.torproject.org/legacy/trac/-/issues/21377DirAuths should expose bwauth bandwidth files2022-02-16T21:12:43ZTom Rittertom@ritter.vgDirAuths should expose bwauth bandwidth filesCurrently, DirAuths that vote on bwauth files do not expose the raw voting file they used. This data would be good to archive for debugging and transparency purposes.Currently, DirAuths that vote on bwauth files do not expose the raw voting file they used. This data would be good to archive for debugging and transparency purposes.Tor: 0.4.0.x-finaljugajugahttps://gitlab.torproject.org/legacy/trac/-/issues/15421Relay crash when reloading and resolv.conf is empty2020-06-13T14:44:32ZTvdWRelay crash when reloading and resolv.conf is empty```
Mar 21 00:11:06 hostnaem Tor[1907]: Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (6)
Mar 21 00:11:06 hostnaem Tor[1907]: set_options(): Bug: Acting on config options left us in a broken state. Dying.
``...```
Mar 21 00:11:06 hostnaem Tor[1907]: Unable to parse '/etc/resolv.conf', or no nameservers in '/etc/resolv.conf' (6)
Mar 21 00:11:06 hostnaem Tor[1907]: set_options(): Bug: Acting on config options left us in a broken state. Dying.
```
This just happened on my 0.2.7.0-alpha-dev build. resolv.conf contains only a "search" parameter, but no nameservers.Tor: 0.4.0.x-finalNick MathewsonNick Mathewson