Mike Perry wrote:
Thus spake Eddie Cornejo (corn...@gmail.com):
Forgive my ignorance but this seeks rather knee-jerk to me. Maybe I'm
missing something.
Yeah, I believe you're missing the fact that these ports also contain
plaintext passwords than can be used to gain access to information
Roger Dingledine wrote:
Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
main other change is a slight tweak to Tor's TLS handshake that makes
relays and bridges that run this new version reachable from Iran again.
We don't expect this tweak will win the arms race
Dear Damian,
with revision 24158 I am getting the following error when I want to run arm.
# ./arm
Traceback (most recent call last):
File ./src/starter.py, line 378, in module
controller.init(conn)
File /arm/src/util/torTools.py, line 292, in init
Damn, looks like the bin function is new in Python 2.6:
http://docs.python.org/library/functions.html#bin
Thanks for the catch. In the future please file a trac ticket rather
emailing everyone on or-talk. Cheers! -Damian
On Sun, Jan 30, 2011 at 12:25 AM, Paul Menzel
On Sun, 30 Jan 2011 12:48:02 +0330
Hasan mhaliz...@gmail.com wrote:
*I have download the new version from
https://www.torproject.org/download/download but still i can't connect to
tor!! :(*
Tor 0.2.2.22-alpha contains 'a slight tweak ... that makes *relays and
bridges* that run this new
At some point, we intend to shrink exit policies further as Tor scales
to more decentralized schemes. Those exit policies will likely be
represented as bits representing subsets of ports. When that time
comes, we will very likely combine encrypted and unencrypted versions
of ports together,
The five relays Mike mentioned have been flagged as BadExits [1].
Adding them to your ExcludeExitNodes isn't necessary. -Damian
[1] https://trac.torproject.org/projects/tor/wiki/badRelays
On Sun, Jan 30, 2011 at 1:33 AM, Jan Weiher j...@buksy.de wrote:
At some point, we intend to shrink exit
On Sun, 30 Jan 2011 10:33:31 +0100
Jan Weiher j...@buksy.de wrote:
At some point, we intend to shrink exit policies further as Tor scales
to more decentralized schemes. Those exit policies will likely be
represented as bits representing subsets of ports. When that time
comes, we will very
2011/1/30 Damian Johnson atag...@gmail.com:
The five relays Mike mentioned have been flagged as BadExits [1].
Adding them to your ExcludeExitNodes isn't necessary. -Damian
That was really dumb, as it puts a lot more load on the Nodes that
support encryption, and, as was mentioned before,
On 01/30/2011 01:56 AM, morphium wrote:
2011/1/30 Damian Johnson atag...@gmail.com:
The five relays Mike mentioned have been flagged as BadExits [1].
Adding them to your ExcludeExitNodes isn't necessary. -Damian
That was really dumb, as it puts a lot more load on the Nodes that
support
Thanks, I see the site was up this earlier, but the gpg call still
failed (using gpg 1.4.10)
Have written a loop to keep trying to grab it...
~chris
On 30 January 2011 00:47, Andrew Lewis and...@pdqvpn.com wrote:
Yeah, that server seems to timeout time to time. Retry it a few times and it
*Thanks for your attention*
*but when I run Tor I receive these warnings:*
*[Warning] Problem bootstrapping. Stuck at 10%: Finishing handshake with
directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1;
recommendation warn)*
*[Notice] No current certificate known for
On Sat, 2011-01-29 at 22:45 -0800, Mike Perry wrote:
Thus spake Eddie Cornejo (corn...@gmail.com):
Forgive my ignorance but this seeks rather knee-jerk to me. Maybe I'm
missing something.
Yeah, I believe you're missing the fact that these ports also contain
plaintext passwords than
On Sat, Jan 29, 2011 at 07:46:20PM +0100, Jan Weiher wrote:
Hi,
while scrolling through the tor status page (torstatus.blutmagie.de), I
stumpled upon the following node (the reason why it came to my eye was
the long uptime):
gatereloaded 550C C972 4FA7 7C7F 9260 B939 89D2 2A70 654D 3B92
Damian Johnson wrote:
The five relays Mike mentioned have been flagged as BadExits [1].
Adding them to your ExcludeExitNodes isn't necessary. -Damian
[1] https://trac.torproject.org/projects/tor/wiki/badRelays
On Sun, Jan 30, 2011 at 1:33 AM, Jan Weiher j...@buksy.de wrote:
At some point,
Hi,
I was wondering if anyone has succeeded torifyng Mixminion.
usewithtor output:
$ usewithtor mixminion send -t x...@.zzz -i data.asc
libtorsocks: The symbol res_send() was not found in any shared library.
The error reported was: not found!
Mixminion version 0.0.8alpha3
This software is
There's no point in putting relays flagged as BadExit into your torrc
since your client will already avoid them. However, if you want a
listing of the bad exits then it's available at:
https://trac.torproject.org/projects/tor/wiki/badRelays
As for the previous discussion of if plaintext-only
On Sat, 29 Jan 2011 10:24 -0600, David Carlson
carlson...@sbcglobal.net wrote:
Hi,
I am forbidden to access the server yelp.com. Is that because I am a
Tor exit node?
Thanks
David
I can confirm this, after accidentally running an exit for a while.
There is a mailto link on the 403
On 30/01/11 02:32, and...@torproject.org wrote:
On Fri, Jan 28, 2011 at 11:29:25PM +, pump...@cotse.net wrote 2.3K bytes in
53 lines about:
: My understanding is that Tor encrypts both the content of a data
: packet and also the header. It encrypts the packet and header three
: times on
On Sun, 30 Jan 2011 22:33:21 +
Matthew pump...@cotse.net wrote:
On 30/01/11 02:32, and...@torproject.org wrote:
On Fri, Jan 28, 2011 at 11:29:25PM +, pump...@cotse.net wrote 2.3K
bytes in 53 lines about:
: My understanding is that Tor encrypts both the content of a data
: packet
Each relay removes one layer of encryption.
Tor does *not* encrypt and send packet headers. Tor only relays the
data within a TCP connection.
I'm still not getting this. My understanding is that you have the data and
the header when using TCP. If only the data is encrypted then what
On Sun, 30 Jan 2011 23:15:17 +
Matthew pump...@cotse.net wrote:
I'm still not getting this. My understanding is that you have the
data and the header when using TCP. If only the data is encrypted
then what happens to the headers?
Does this image help at all?
Each relay removes one layer of encryption.
Tor does *not* encrypt and send packet headers. Tor only relays the
data within a TCP connection.
OK. I get it. I think.
Please confirm:
The data is encrypted. The header is not encrypted.
So if my ISP is monitoring my traffic all they see
On Sun, 30 Jan 2011 23:33 +, Matthew pump...@cotse.net wrote:
Each relay removes one layer of encryption.
Tor does *not* encrypt and send packet headers. Tor only relays the
data within a TCP connection.
OK. I get it. I think.
Please confirm:
The data is encrypted. The
I'm aware of the fact that it is not recommended to use tor without
additional encryption, but some users do. And I dont see any reason for
only allowing unencrypted traffic than snooping?
[...]
I don't see why any of this really matters. Anyone running tor should have
the good sense to
On Sun, 30 Jan 2011 22:59:49 +
Geoff Down geoffd...@fastmail.net wrote:
how do I report a bug with the Polipo in
https://www.torproject.org/dist/vidalia-bundles/vidalia-bundle-0.2.2.22-alpha-0.2.10-ppc.dmg
?
And how do I tell which version is in there also please?
If that bundle contains
On Sun, 30 Jan 2011 16:20 -0800, Robert Ransom
rransom.8...@gmail.com wrote:
On Sun, 30 Jan 2011 22:59:49 +
Geoff Down geoffd...@fastmail.net wrote:
how do I report a bug with the Polipo in
https://www.torproject.org/dist/vidalia-bundles/vidalia-bundle-0.2.2.22-alpha-0.2.10-ppc.dmg
Thus spake morphium (morph...@morphium.info):
2011/1/30 Damian Johnson atag...@gmail.com:
The five relays Mike mentioned have been flagged as BadExits [1].
Adding them to your ExcludeExitNodes isn't necessary. -Damian
That was really dumb, as it puts a lot more load on the Nodes that
( I saw http://archives.seul.org/or/talk/Jan-2011/msg00161.html but it
doesn't specify where the new bugtracker is).
We do not know of any new bug tracker for Polipo. If you have a bug
report for Polipo itself, report it to the polipo-users mailing list
(see
On 1/30/2011 1:53 PM, Geoff Down wrote:
On Sat, 29 Jan 2011 10:24 -0600, David Carlson
carlson...@sbcglobal.net wrote:
Hi,
I am forbidden to access the server yelp.com. Is that because I am a
Tor exit node?
Thanks
David
I can confirm this, after accidentally running an exit for a
30 matches
Mail list logo
