Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T14:02:11Zhttps://gitlab.torproject.org/legacy/trac/-/issues/48assertion failure: resolve->pending_connection2020-06-13T14:02:11ZNick Mathewsonassertion failure: resolve->pending_connectionReported by Giorgos P.
Dec 31 07:50:01.038 [err] dns.c:399: dns_cancel_pending_resolve:
Assertion resolve->pending_connections failed; aborting.
_probably_ unrelated to other warning:
Dec 30 15:46:29.338 [warn] connection_dns_reached_...Reported by Giorgos P.
Dec 31 07:50:01.038 [err] dns.c:399: dns_cancel_pending_resolve:
Assertion resolve->pending_connections failed; aborting.
_probably_ unrelated to other warning:
Dec 30 15:46:29.338 [warn] connection_dns_reached_eof(): Read eof.
Worker died unexpectedly.
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/legacy/trac/-/issues/47Why does the win32 installer have a click-through license?2020-06-13T14:36:29ZRoger DingledineWhy does the win32 installer have a click-through license?Our license is permissive, that is, it only grants rights,
it does not grant rights in exchange for giving up other
rights. So why do we require users to acknowledge that
they "agree" to it?
[Automatically added by flyspray2trac: Operat...Our license is permissive, that is, it only grants rights,
it does not grant rights in exchange for giving up other
rights. So why do we require users to acknowledge that
they "agree" to it?
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/46Wiki table of contents doesn't use our anchors2020-06-13T17:18:05ZRoger DingledineWiki table of contents doesn't use our anchorsThe FAQ wiki points to these big hash anchors rather than
the [[Anchor]] elements we added. Can we make it so it's
more obvious that we have human-usable anchors in the page
too?
[Automatically added by flyspray2trac: Operating System: ...The FAQ wiki points to these big hash anchors rather than
the [[Anchor]] elements we added. Can we make it so it's
more obvious that we have human-usable anchors in the page
too?
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/legacy/trac/-/issues/45win32 torrc contains automake macros2020-06-13T14:02:11ZRoger Dingledinewin32 torrc contains automake macrosThe entries in the torrc that ships with win32 still contain
macros like @LOCALSTATEDIR@, which win32 users don't know
what to do with. This makes it really hard for them to, e.g.,
configure logs. Can we convert them to a reasonable set ...The entries in the torrc that ships with win32 still contain
macros like @LOCALSTATEDIR@, which win32 users don't know
what to do with. This makes it really hard for them to, e.g.,
configure logs. Can we convert them to a reasonable set of
defaults on win32 before shipping?
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]0.0.9.5Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/44resolve_my_address() failures can lead to crash.2020-06-13T14:07:13ZNick Mathewsonresolve_my_address() failures can lead to crash.If resolve_my_address() fails at a HUP, then rather than continuing with the old address (desirable if the address hasn't changed) or exiting gracefully (maybe desirable if the address has changed), Tor simply crashes at places like
ma...If resolve_my_address() fails at a HUP, then rather than continuing with the old address (desirable if the address hasn't changed) or exiting gracefully (maybe desirable if the address has changed), Tor simply crashes at places like
main.c: if (write_str_to_file(keydir,
router_get_my_descriptor(), 0)) {
This should get fixed.
Reported by Ben L.
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/legacy/trac/-/issues/43Worker threads die vigorously on win32.2020-06-13T14:02:11ZNick MathewsonWorker threads die vigorously on win32.When people try to run a Tor server on windows, it seems that their CPU worker threads and DNS threads too die badly. Or maybe the tor_socketpair stuff isn't really working.
[...]
Dec 25 07:55:03.156 [warn] connection_dns_reached_eof(...When people try to run a Tor server on windows, it seems that their CPU worker threads and DNS threads too die badly. Or maybe the tor_socketpair stuff isn't really working.
[...]
Dec 25 07:55:03.156 [warn] connection_dns_reached_eof(): Read eof. Worker died unexpectedly.
Dec 25 07:55:03.156 [warn] connection_cpu_reached_eof(): Read eof. Worker died unexpectedly.
[...]
Also, these dead workers don't prevent Tor from reporting itself as working when the first circuit is built. That's probably bad.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]https://gitlab.torproject.org/legacy/trac/-/issues/42Overzealous clock skew checking keeps clients from working2020-06-13T14:02:11ZNick MathewsonOverzealous clock skew checking keeps clients from workingThe check for time skew in connection_or.c which produces the log message: "Router '%s' (%s:%d) has a skewed clock..." seems to get called even when Tor is running as a client. This is not as intended; only servers should be forced to m...The check for time skew in connection_or.c which produces the log message: "Router '%s' (%s:%d) has a skewed clock..." seems to get called even when Tor is running as a client. This is not as intended; only servers should be forced to make sure their clocks are relatively correct.
Arma questions whether we should care about clock skew at all. The attacks that we're protecting against are server impersonation attacks where the attacker manage to compromise an older private key for a server, but not a newer one. This doesn't seem very realistic now, since compromising a server's private key will almost surely reveal its identity key; but a slightly cleverer key management system might in the future make this attack meaningfully difficult.
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/legacy/trac/-/issues/41nickname length enforcement has fencepost errors2020-06-13T14:02:11ZRoger Dingledinenickname length enforcement has fencepost errorsDec 23 19:08:53.410 [warn] connection_tls_finish_handshake(): Other side (80.127.47.237:9001) is 'thetimesareachangi', but we tried to connect to 'thetimesareachangin'
It should either not have a problem here, or it should have prevente...Dec 23 19:08:53.410 [warn] connection_tls_finish_handshake(): Other side (80.127.47.237:9001) is 'thetimesareachangi', but we tried to connect to 'thetimesareachangin'
It should either not have a problem here, or it should have prevented this guy from starting his server.
Once we track down which it is, we should audit the rest of the uses of options->nickname to make sure it isn't happening elsewhere.
[Automatically added by flyspray2trac: Operating System: All]Nick MathewsonNick Mathewson