Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2012-01-23T16:55:11Zhttps://gitlab.torproject.org/legacy/trac/-/issues/3064Vidalia stores ControlPassword as plaintext2012-01-23T16:55:11ZTracVidalia stores ControlPassword as plaintextAs in object , but I don't really know if this should be treated as a real bug or a feature
**Trac**:
**Username**: tornewbieAs in object , but I don't really know if this should be treated as a real bug or a feature
**Trac**:
**Username**: tornewbieTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/2757Bug: Duplicate call to connection_mark_for_close2020-06-13T14:09:31ZTracBug: Duplicate call to connection_mark_for_closeDebian SID , x86 machine
Tor 0.2.3.0-alpha-dev (git-d52a99dc77dc7700)
OpenSSL 1.0.0c ( experimental )
libevent 2.0.10 ( experimental )
Self compiled , shared libraries , tor running as a client only.
I found this warnings in tor lo...Debian SID , x86 machine
Tor 0.2.3.0-alpha-dev (git-d52a99dc77dc7700)
OpenSSL 1.0.0c ( experimental )
libevent 2.0.10 ( experimental )
Self compiled , shared libraries , tor running as a client only.
I found this warnings in tor logs :
[warn] Rejecting request for anonymous connection to private address [scrubbed] on a TransPort or NATDPort. Possible loop in your NAT rules?
[warn] Bug: Duplicate call to connection_mark_for_close at connection.c:1225 (first at connection_edge.c:1680)
The first warn is pretty normal because I was running tor as a
transparent proxy for a single user on a single machine in my local
net and I was connected to it by ssh with X forwarding : of course
tor refused to forward X protocol ( indeed , I have a specific iptables rule for permitting that , which I forgot to set in this case) but the call for closing the connection is duplicated/redundant.
**Trac**:
**Username**: tornewbieTor: 0.2.2.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/3105Pushed bytes reported by Heartbeat are wrong with bufferevents enabled2020-06-13T14:10:21ZTracPushed bytes reported by Heartbeat are wrong with bufferevents enabled[notice] Tor 0.2.3.0-alpha-dev (git-b0a7e0d6ca45bef3)
...
[notice] Heartbeat: Tor's uptime is 6:00, with 2 circuits open. I've pushed 4.00 GB and received 18.01 MB.
...
[notice] Heartbeat: Tor's uptime is 12:00, with 2 circuits open. I'v...[notice] Tor 0.2.3.0-alpha-dev (git-b0a7e0d6ca45bef3)
...
[notice] Heartbeat: Tor's uptime is 6:00, with 2 circuits open. I've pushed 4.00 GB and received 18.01 MB.
...
[notice] Heartbeat: Tor's uptime is 12:00, with 2 circuits open. I've pushed 8.00 GB and received 23.94 MB
**Trac**:
**Username**: tornewbieTor: unspecifiedSebastian HahnSebastian Hahnhttps://gitlab.torproject.org/legacy/trac/-/issues/3126Hidden services (web based only ? ) are not accessible through Tor Transparen...2020-06-13T14:10:25ZTracHidden services (web based only ? ) are not accessible through Tor Transparent ProxyJust reading this on the talk list : https://lists.torproject.org/pipermail/tor-talk/2011-May/020323.html
I've seen the same behaviour while trying to access any (web) hidden service through Tor Transparent Proxy function.
I've setup a...Just reading this on the talk list : https://lists.torproject.org/pipermail/tor-talk/2011-May/020323.html
I've seen the same behaviour while trying to access any (web) hidden service through Tor Transparent Proxy function.
I've setup a user , I've configured Tor following this guide : https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TransparentProxy#Transparentlyanonymizingtrafficforaspecificuser , then launched iceweasel in a separate session for the anonymized user but can't connect to any hidden service.
And dig resolves any hidden service to 127.192.0.x as described in the message linked on the top.
**Trac**:
**Username**: tornewbieRobert RansomRobert Ransomhttps://gitlab.torproject.org/legacy/trac/-/issues/3566Should controller events respect SafeLogging 1 torrc option?2020-06-13T14:11:51ZTracShould controller events respect SafeLogging 1 torrc option?Vidalia seems not to scrub addresses ignoring SafeLogging directive set in the torrc config file : the first one is the event logged by Vidalia , the second one is the same event logged by Tor while pulling tor git tree with tsocks ( 'us...Vidalia seems not to scrub addresses ignoring SafeLogging directive set in the torrc config file : the first one is the event logged by Vidalia , the second one is the same event logged by Tor while pulling tor git tree with tsocks ( 'usewithtor git pull' on the command line )
[...same time...] Potentially Dangerous Connection! - One of your applications established a connection through Tor to "38.229.70.11:9418" using a protocol that may leak information about your destination. Please ensure you configure your applications to use only SOCKS4a or SOCKS5 with remote hostname resolution.
...same time... [warn] Your application (using socks5 to port 9418) is giving Tor only an IP address. Applications that do DNS resolves themselves may leak information. Consider using Socks4A (e.g. via privoxy or socat) instead. For more information, please see https://wiki.torproject.org/TheOnionRouter/TorFAQ#SOCKSAndDNS.
**Trac**:
**Username**: tornewbieTor: unspecifiedTomas ToucedaTomas Toucedahttps://gitlab.torproject.org/legacy/trac/-/issues/4043Provide an option to get rid of relays running a non reccomended version of tor2020-06-13T14:13:21ZTracProvide an option to get rid of relays running a non reccomended version of torThere are some relays , some temporary other stable ones, which are running old versions of tor ( mainly Tor 0.2.1.29 (r318f470bc5f2ad43) ) and with a recent enough uptime ... eg :
- a French relay named cannabis ( now disappeared )
- a...There are some relays , some temporary other stable ones, which are running old versions of tor ( mainly Tor 0.2.1.29 (r318f470bc5f2ad43) ) and with a recent enough uptime ... eg :
- a French relay named cannabis ( now disappeared )
- a British relay named PorkLegs ( now disappeared )
- https://torstatus.blutmagie.de/router_detail.php?FP=2624ae0466bd02afaf3f263d4361d79abe0e7e05
- https://torstatus.blutmagie.de/router_detail.php?FP=2ec76bb33df489adebd17f0e9cdc5ec0d6a00482
- https://torstatus.blutmagie.de/router_detail.php?FP=170f58d502a7df3675872c9ae18299e666598a0d
- https://torstatus.blutmagie.de/router_detail.php?FP=1d8625690ab9729fb2040d8194ec0d6789a4d092
Maybe I'm wrong but I don't see any good reason to start running a high bandwidth relay with an old and not reccomended version of tor than exploiting old vulnerabilities and trying using them to deanonimize tor users.
**Trac**:
**Username**: tornewbieTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/8553get_net_param_from_list(): Bug: src/or/networkstatus.c:2192: get_net_param_fr...2020-06-13T14:28:24ZTracget_net_param_from_list(): Bug: src/or/networkstatus.c:2192: get_net_param_from_list: Assertion min_val <= default_val failed;Maybe there was something going wrong between commits 6e94d2fb3a11d7cb and 7c2eabcf8e68aee1 :
```
[...] [notice] Tor 0.2.5.0-alpha-dev (git-7c2eabcf8e68aee1) opening log file.
[...] [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip...Maybe there was something going wrong between commits 6e94d2fb3a11d7cb and 7c2eabcf8e68aee1 :
```
[...] [notice] Tor 0.2.5.0-alpha-dev (git-7c2eabcf8e68aee1) opening log file.
[...] [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
[...] [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
[...] [notice] This version of Tor (0.2.5.0-alpha-dev) is newer than any recommended version, according to the directory authorities. Recommended versions are: 0.2.2.39,0.2.3.24-rc,0.2.3.25,0.2.4.5-alpha,0.2.4.6-alpha,0.2.4.7-alpha,0.2.4.8-alpha,0.2.4.9-alpha,0.2.4.10-alpha,0.2.4.11-alpha
[...] [notice] We now have enough directory information to build circuits.
[...] [notice] Bootstrapped 80%: Connecting to the Tor network.
[...] [err] get_net_param_from_list(): Bug: src/or/networkstatus.c:2192: get_net_param_from_list: Assertion min_val <= default_val failed; aborting.
```
```
[...] [notice] Tor 0.2.5.0-alpha-dev (git-6e94d2fb3a11d7cb) opening log file.
[...] [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
[...] [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
[...] [notice] This version of Tor (0.2.5.0-alpha-dev) is newer than any recommended version, according to the directory authorities. Recommended versions are: 0.2.2.39,0.2.3.24-rc,0.2.3.25,0.2.4.5-alpha,0.2.4.6-alpha,0.2.4.7-alpha,0.2.4.8-alpha,0.2.4.9-alpha,0.2.4.10-alpha,0.2.4.11-alpha
[...] [notice] We now have enough directory information to build circuits.
[...] [notice] Bootstrapped 80%: Connecting to the Tor network.
[...] [notice] Bootstrapped 85%: Finishing handshake with first hop.
[...] [notice] Bootstrapped 90%: Establishing a Tor circuit.
[...] [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
[...] [notice] Bootstrapped 100%: Done.
```
**Trac**:
**Username**: tornewbieTor: 0.2.4.x-final