Re: [tor-talk] Debian-tor 0.2.2.34-1~~squeeze+1 PID/UID bug

2011-10-29 Thread Orionjur Tor-admin
On 28.10.2011 19:48, unknown wrote: > On Fri, 28 Oct 2011 18:52:12 + > unknown wrote: > > >> Sorry for the misinformation. ps aux always displays numerical ID's for long >> usernames. >> I trying to repeat this situation on another Debian Linux machine with >> similar versions updates an

Re: [tor-talk] bug found on the Tor v0.2.3.6-alpha (git-47dff61061f4bfc2).

2011-10-29 Thread Eugen Leitl
On Sat, Oct 29, 2011 at 09:58:53AM +0200, Klaus Layer wrote: > Roger Dingledine wrote on 28.10.2011: > > > > That bug is https://trac.torproject.org/projects/tor/ticket/4299 > > > > The more exciting one is > > https://trac.torproject.org/projects/tor/ticket/4343 > > which looks related except T

Re: [tor-talk] bug found on the Tor v0.2.3.6-alpha (git-47dff61061f4bfc2).

2011-10-29 Thread Klaus Layer
Roger Dingledine wrote on 28.10.2011: > > That bug is https://trac.torproject.org/projects/tor/ticket/4299 > > The more exciting one is > https://trac.torproject.org/projects/tor/ticket/4343 > which looks related except Tor crashes. Same here. I updated yesterday and all TOR instances are crash

Re: [tor-talk] Encrypted service ports (Was: bug found on the Tor v0.2.3.6-alpha (git-47dff61061f4bfc2).)

2011-10-29 Thread Julian Yon
On 29/10/11 09:29, Eugen Leitl wrote: > Unrelated question, does someone have a good exit policy for > the usual ports for *encrypted* services? I currently have these rules for encrypted services: ExitPolicy accept *:22 # ssh ExitPolicy accept *:443 # https ExitPolicy accept *:465 # ssmtp ExitPo

Re: [tor-talk] bug found on the Tor v0.2.3.6-alpha (git-47dff61061f4bfc2).

2011-10-29 Thread Nick Mathewson
On Fri, Oct 28, 2011 at 4:23 PM, Roger Dingledine wrote: > On Fri, Oct 28, 2011 at 03:09:38PM -0500, Jon wrote: >> Oct 28 07:51:21.106 [Notice] Tor v0.2.3.6-alpha >> (git-47dff61061f4bfc2). This is experimental software. Do not rely on >> it for strong anonymity. (Running on Windows 7 Service Pack

Re: [tor-talk] bug found on the Tor v0.2.3.6-alpha (git-47dff61061f4bfc2).

2011-10-29 Thread Tim Wilde
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/29/2011 9:18 AM, Nick Mathewson wrote: > These bugs should now be fixed in the git repository. Looks like > we're chasing down a couple more, though, related to geoip and/or > limited windows users. > > Sorry for the trouble; hope we can get

Re: [tor-talk] bug found on the Tor v0.2.3.6-alpha (git-47dff61061f4bfc2).

2011-10-29 Thread Nick Mathewson
Thanks, Tim! If you aren't on windows, and you're comfortable building from source, I'd ask if you can try out the latest version of either the master branch or the maint-0.2.2 branch. I *think* we've got the known non-windows issues pretty well squashed there, so more testing to try to discover

Re: [tor-talk] bug found on the Tor v0.2.3.6-alpha (git-47dff61061f4bfc2).

2011-10-29 Thread Tim Wilde
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/29/2011 10:43 AM, Nick Mathewson wrote: > If you aren't on windows, and you're comfortable building from > source, I'd ask if you can try out the latest version of either the > master branch or the maint-0.2.2 branch. I *think* we've got the > k

[tor-talk] Question about Vidalia Exit Bundle

2011-10-29 Thread David Carlson
The last few times that I have updated my (Windows)Vidalia Exit Bundle I have found that it changed my torrc even though I deliberately selected to not replace it during the install. Specifically, it deleted my nickname and deleted my exit policy. How can I prevent that? David 0xDC7C8BF3.asc D

[tor-talk] abnormal bridge usage since September

2011-10-29 Thread Lu Wei
Stumbled upon metrics.torproject.org/users.html , and found an interesting thing about the graph of "Tor users via bridges". There's a burst of bridge usage since about September 25, which correspond with the recent spasm of chinese gfw, and extensive failure of GIFC's products. My first impression

Re: [tor-talk] bug found on the Tor v0.2.3.6-alpha (git-47dff61061f4bfc2).

2011-10-29 Thread Jim
Nick Mathewson wrote: Thanks, Tim! If you aren't on windows, and you're comfortable building from source, I'd ask if you can try out the latest version of either the master branch or the maint-0.2.2 branch. I *think* we've got the known non-windows issues pretty well squashed there, so more