Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:40:27Zhttps://gitlab.torproject.org/legacy/trac/-/issues/30084Relay: channel_tls_process_netinfo_cell private IP as public wrongly reported2020-06-13T15:40:27ZcypherpunksRelay: channel_tls_process_netinfo_cell private IP as public wrongly reportedLog output:
Nov 06 17:11:10.000 [info] {OR} channel_tls_process_netinfo_cell(): We made a connection to a relay at 92.167.89.160:9001 (fp=427E5C8ADC43B09582DDDA80EA8EDFBD05DF5003) but we think they will not consider this connection canon...Log output:
Nov 06 17:11:10.000 [info] {OR} channel_tls_process_netinfo_cell(): We made a connection to a relay at 92.167.89.160:9001 (fp=427E5C8ADC43B09582DDDA80EA8EDFBD05DF5003) but we think they will not consider this connection canonical. They think we are at 10.42.194.61, but we think its
92.222.41.125.
Nov 06 17:30:35.000 [info] {OR} channel_tls_process_netinfo_cell(): Got good NETINFO cell from 92.167.89.160:9001; OR connection is now open, using protocol version 5. Its ID digest is 033DC13D5639A530C098388D8F53A693D76AD59B. Our address is apparently
10.42.194.61.
10.42.194.61 does not exist in Intranet. It's reported wrongly by remote relay.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/19064Access denied, by most exits, to a very specific IP range2016-05-27T09:45:33ZTracAccess denied, by most exits, to a very specific IP rangeThe IP ranges in and around 162.216.5.226 (although is seems to be generalize around, approximately, 162.216.5.224/28) are blocked from the majority of TOR nodes. I have tried a wide variety of "new TOR circuits", and nearly all of them...The IP ranges in and around 162.216.5.226 (although is seems to be generalize around, approximately, 162.216.5.224/28) are blocked from the majority of TOR nodes. I have tried a wide variety of "new TOR circuits", and nearly all of them have such a block in place. This includes http (port 80), https (port 443), DNS (port 53), and other likely ports, (i.e. cPanel).
I have equally tested through a quantity of free proxies (not TOR related), and blocks do not exist to this IP range through any of them.
All indications are that this block by TOR began on, or shortly after 24 April 2015.
**Trac**:
**Username**: Tu2020https://gitlab.torproject.org/legacy/trac/-/issues/16347TOR Browser Favicon.ico IP leak2020-06-15T23:26:46ZTracTOR Browser Favicon.ico IP leakAttached are logs for TOR Browser sessions during the logging into Buffalo Terastation TS-XEL with firmware version 1.55. The logs are from Terastation lighttpd.webui.access.log.
Version of TOR Browser was likely 4.5, it was the version...Attached are logs for TOR Browser sessions during the logging into Buffalo Terastation TS-XEL with firmware version 1.55. The logs are from Terastation lighttpd.webui.access.log.
Version of TOR Browser was likely 4.5, it was the version which updated itself automatically from TOR Browser. It was certainly below 4.5.1, because an access occured before May 13.
TOR client IP address is XXX.XXX.XXX.XXX.
Target IP address is YYY.YYY.YYY.YYY.
Real IP address is ZZZ.ZZZ.ZZZ.ZZZ, it was checked and confirmed with ISP.
Based on access circumstances, it is unthinkable that a target was "accidentally" accessed via a standard browser at that time, which was IE11.
What is strange for real User-Agent is that it is listed as Windows NT 6.2. But real version of Windows was NT 6.3.
Below is a small fragment of the logs:
XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY - [Date:19:15:53 +0900] "POST /dynamic.pl HTTP/1.1" 200 192 "http://YYY.YYY.YYY.YYY/static/root.html" "Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0"
XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY - [Date:19:15:53 +0900] "GET /static/ext/resources/images/default/grid/grid3-hrow.gif HTTP/1.1" 200 836 "http://YYY.YYY.YYY.YYY/static/ext/resources/css/ext-all.css" "Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0"
XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY - [Date:19:15:53 +0900] "GET /static/ext/resources/images/default/s.gif HTTP/1.1" 200 43 "http://YYY.YYY.YYY.YYY/static/root.html" "Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0"
XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY - [Date:19:16:08 +0900] "GET /static/ext/resources/images/default/grid/row-over.gif HTTP/1.1" 200 823 "http://YYY.YYY.YYY.YYY/static/ext/resources/css/ext-all.css" "Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0"
XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY - [Date:19:16:08 +0900] "GET /static/ext/resources/images/default/grid/grid3-hrow-over.gif HTTP/1.1" 200 823 "http://YYY.YYY.YYY.YYY/static/ext/resources/css/ext-all.css" "Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0"
ZZZ.ZZZ.ZZZ.ZZZ YYY.YYY.YYY.YYY - [Date:19:17:20 +0900] "GET /favicon.ico HTTP/1.1" 200 97 "-" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.2; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729)"
XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY - [Date:19:17:51 +0900] "POST /dynamic.pl HTTP/1.1" 200 289 "http://YYY.YYY.YYY.YYY/static/root.html" "Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0"
XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY - [Date:19:17:53 +0900] "GET /dynamic.pl?_dc=1431339247835&bufaction=getRootSettings2 HTTP/1.1" 200 551 "http://YYY.YYY.YYY.YYY/static/root.html" "Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0"
XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY - [Date:19:17:54 +0900] "GET /dynamic.pl?_dc=1431339247838&bufaction=validateSession HTTP/1.1" 200 77 "http://YYY.YYY.YYY.YYY/static/root.html" "Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Firefox/31.0"
**Trac**:
**Username**: torleakhttps://gitlab.torproject.org/legacy/trac/-/issues/6972Double TOR PROJECT2012-09-25T09:31:03ZTracDouble TOR PROJECTHello! :)
Now I'm writing to you because I need help. I put my computer in the TOR, which also starts out nicely, just like the Vidalia control panel should start and then load the TOR Browser is nice and writes that "Congratulations. Y...Hello! :)
Now I'm writing to you because I need help. I put my computer in the TOR, which also starts out nicely, just like the Vidalia control panel should start and then load the TOR Browser is nice and writes that "Congratulations. Your browser is configured to use Tor.". It's been okay, but the problem there was that the two TOR was launched, setting the password so its been 2 Vidalia Control Panel, and 2 Tor Browser.
My question would be:
I know that the two control panel and web browser to separate the two so that two are obtained, which consist of separate identity?
So when I press the control panel quickly both "Use of a New Identity" button, the browser can not both appear in the same ip, but 2 different.
I guess in the ports to play, but there is a simpler solution may be, in any event, I look forward to megoldásaitokat.
Thank you.
**Trac**:
**Username**: Intellektushttps://gitlab.torproject.org/legacy/trac/-/issues/1913Do new IP tests on HUP.2020-06-13T14:06:23ZcypherpunksDo new IP tests on HUP.I run some tor bridges on very dynamic IPs, I would like to send a HUP signal when I receive a new IP and have tor run the IP tests, otherwise takes about 10 or so minutes before the change of IP is discovered by tor.I run some tor bridges on very dynamic IPs, I would like to send a HUP signal when I receive a new IP and have tor run the IP tests, otherwise takes about 10 or so minutes before the change of IP is discovered by tor.