Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2008-07-18T19:01:45Zhttps://gitlab.torproject.org/legacy/trac/-/issues/778Even if US Spoofing is desactivated navigator as an old User Agent2008-07-18T19:01:45ZTracEven if US Spoofing is desactivated navigator as an old User AgentWithout Tor ( No Tor mode)
HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16
HTTP_ACCEPT_LANGUAGE: fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3
Tor Mode without US Spoofing
HTTP_USER_AGENT...Without Tor ( No Tor mode)
HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16
HTTP_ACCEPT_LANGUAGE: fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3
Tor Mode without US Spoofing
HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
HTTP_ACCEPT_LANGUAGE: fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3
Tor Mode with US Spoofing
HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5
All without restart of Firefox. Could give help to the traffic partition analyser.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: amishttps://gitlab.torproject.org/legacy/trac/-/issues/775tor crash on libevent error2020-06-13T14:00:15ZTractor crash on libevent errorJul 15 03:44:56.239 [notice] Tor 0.2.0.28-rc (r15188) opening new log file.
...
Jul 15 18:53:24.691 [err] Error from libevent: event_queue_remove: 0x9c331c38(fd 0) not on queue 1
...
Jul 17 11:58:35.282 [notice] Tor 0.2.1.2-alpha (r15383...Jul 15 03:44:56.239 [notice] Tor 0.2.0.28-rc (r15188) opening new log file.
...
Jul 15 18:53:24.691 [err] Error from libevent: event_queue_remove: 0x9c331c38(fd 0) not on queue 1
...
Jul 17 11:58:35.282 [notice] Tor 0.2.1.2-alpha (r15383) opening log file.
...
Jul 17 23:33:22.515 [err] Error from libevent: event_queue_remove: 0xb2797c38(fd 0) not on queue 1
Hello,
since the last two days i've the same error on mxr running on a debian hardy with all standard scripts.
I've no change in the config since some days.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: amishttps://gitlab.torproject.org/legacy/trac/-/issues/748Limit verbosity of [warn] Failing because we have 991 connections already. Pl...2020-06-13T14:00:11ZTracLimit verbosity of [warn] Failing because we have 991 connections already. Please raise your ulimitHello, on a standard log Tor usage ( notice mode only) the verbosity of
[warn] Failing because we have 991 connections already. Please raise your ulimit -n.
Can block a server by disk /var saturation.
Yes, i now w that you can separe t...Hello, on a standard log Tor usage ( notice mode only) the verbosity of
[warn] Failing because we have 991 connections already. Please raise your ulimit -n.
Can block a server by disk /var saturation.
Yes, i now w that you can separe that, and make a good machine configuration,
but all we experienced that many users are not like that.
So can we reduce logs like that to something like ( repeted x times).
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: amishttps://gitlab.torproject.org/legacy/trac/-/issues/697Wrong DNS configuration could break navigation2020-06-13T14:00:00ZTracWrong DNS configuration could break navigationOn 0.2.0.26rc (add new version on reported version please),
Hello,
i've received one email who alert me.
One user have received OpenDNS pages when he is using tor.
OpenDNS is a company who resolve DNS for the others giving them filt...On 0.2.0.26rc (add new version on reported version please),
Hello,
i've received one email who alert me.
One user have received OpenDNS pages when he is using tor.
OpenDNS is a company who resolve DNS for the others giving them filtering, security, ads, but no privacy.
It appears that some nodes resolving DNS seems to have wrong DNS configured, blocking navigation.
If one router making dns resolution is misconfigured it could break navigation of others.
I think a DNS control need probably to be added making theses routers down.
Perhaps using a downloadable list for phishing.
---------- Forwarded message ----------
From: d
Date: 2008/6/10 04:22
Subject: Tor exit node policy
Hello,
I was browsing a phishing site using Tor recently and instead of the phish I saw an OpenDNS warning page (and apparently no way to bypass it). Yours was one of the exit nodes that was part of my Tor connection at the time.
I wasn't able to identify exactly which exit node it was.
Do you have Phish Filtering set up on your exit node, and if so is this a deliberate policy? I work in antiphishing and use Tor for some phish sites.
Thank you,
d
----------------------
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: amisTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/690Increase the security by adding Relays from the same provider to the same family2020-06-13T13:59:57ZTracIncrease the security by adding Relays from the same provider to the same familyHi
Many routers runned on the same provider could break security used in the same circuit.
Even if the is the /16 auto exclude and the Family declaration, it's seems there isn't any control of the provider traffic analysis.
We could se...Hi
Many routers runned on the same provider could break security used in the same circuit.
Even if the is the /16 auto exclude and the Family declaration, it's seems there isn't any control of the provider traffic analysis.
We could see in the directory many routers from the same provider with asn't the same /16 network.
It should be great to give directories to auto add families to OR from the same provider based on the RIPE registry AS number of the smallest IP range.
Perhaps should be better operated only by authorities directories.
Examples of multiples /16 from the word:
virtual.com.br 189.5 189.61 189.33 ...
brasiltelecom.net.br 200.180 201.3 201.24
hispeed.ch 84.75. 87.73. 85.2.
proxad.net
wanadoo.fr
chello.pl
t-dialin.net ...
Regards
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: amishttps://gitlab.torproject.org/legacy/trac/-/issues/689Add Bogon network to the default reject policy2020-06-13T13:59:57ZTracAdd Bogon network to the default reject policyIP from the bogon list could be found in the current directory:
1.1.1.1 1.1.1.2 39.x.x.X
Add the bogon network list in the default reject policy could be good.
If i don't think there is, an accept policy most of these IP could be added...IP from the bogon list could be found in the current directory:
1.1.1.1 1.1.1.2 39.x.x.X
Add the bogon network list in the default reject policy could be good.
If i don't think there is, an accept policy most of these IP could be added.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: amishttps://gitlab.torproject.org/legacy/trac/-/issues/688Change on Band inside torrc aren't published on reload2020-06-13T13:59:57ZTracChange on Band inside torrc aren't published on reloadin 0.2.0.26rc
Process
modify one of this line:
RelayBandwidthRate 1000 KBytes # Throttle traffic to 100KB/s (800Kbps)
RelayBandwidthBurst 2000 KBytes # But allow bursts up to 200KB/s (1600Kbps)
MaxAdvertisedBandwidth 50 KBytes
Then d...in 0.2.0.26rc
Process
modify one of this line:
RelayBandwidthRate 1000 KBytes # Throttle traffic to 100KB/s (800Kbps)
RelayBandwidthBurst 2000 KBytes # But allow bursts up to 200KB/s (1600Kbps)
MaxAdvertisedBandwidth 50 KBytes
Then do a reload of tor /etc/init.d/tor reload
Change above aren't published in the directories.
Tor restart seems to be needed for publishing changes.
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: amisRoger DingledineRoger Dingledine