Privacy Wipe Apps ?
in [Freeware]
|
Prev: u-tube
Next: "Progress" [was: Scanner driver]
From: Sam Luter on 16 Jan 2010 15:56 On Sat, 16 Jan 2010 19:57:43 +0000, hummingbird wrote: > 'JB' wrote thus: > >>Spamblk wrote: >> >>> hummingbird <hummingb�rd(a)127.0.0.1> wrote in >>> news:4cf908a41024569a254c9bbb45e619fe(a)aracari.org: >>> >>> > Packets going from your Tor browser to your ISP are encrypted. >>> >>> To Hummingbird and JB: >>> >>> OK well I haven't actually used TOR so can't pontificate. In my >>> defence I did refer my 2cents worth. >>> >>> You both know a bit more about TOR than I do albeit from >>> differing perspectives. >>> >>> >>I can't see a way you can hide your packets from >>> >>your ISP or Default Gateway which are on the first few network hops >>> > >>> > "first few network hops"? You mean only the 1st hop? (ie: your >>> > ISP to the first Tor node?). >>> >>> Hmm, well I was thinking that beyond your local machine there is >>> at least 2 hops: The default gateway into your ISP's network, >> >>There's a lot more than two. Typically a dozen or more between your >>machine and a remote host. There's 16 between my machine and >>www.google.com right now, for instance. Even surfing to the home >>page of my own ISP (hosted in their IP block) takes 7 hops. >> >>> then there is another hop: the exit point from that network to >>> the entry point of another network which will be another >>> gateway or router(though the same machine can be used to act as >>> the entry and exit points?). Large ISPs might have more than one >>> ring or network also. I was therefore thinking that if you are >>> communicating with a server that isn't on your local network it >>> would require a packet to traverse at least 2 nodes to reach >>> that server. >>> >>> > And if that 1st node does not keep >>> > logs.......what then? Further, IME, Tor nodes change during a >>> > session. I have tested this. >>> > >>> >>(which >>> >>you can view using a utility such as traceroute (TRACERT if using >>> >>MSDOS). >>> > >>> > Not sure how this will help. >>> > Again, IME, Tor nodes change during a session. >>> >>> Very well. >> >>Actually, hummingbird is a bit confused on this point also. A >>collection of Tor nodes is called a "circuit". Tor functions by >>building these circuits and then routing information along them. >>Circuits don't "change during a session", they're changed according >>to certain rules. Some circuits are more "durable" than others, and >>in point of fact, Tor specifically leans toward *not* changing >>circuits in the middle of a session because when you do things like >>that you tend to really screw up communications between hosts. >> >>One of the exceptions to the "don't change" rule is simple HTTP. >>Web browsing normally isn't broken by an IP that's a moving target. >>Web servers are basically "dumb" machines, just sitting there >>spitting out packets to whatever requests that come in regardless >>of where they came from. >> >>Other protocols aren't so tolerant. IRC servers for instance will >>almost invariably boot you if your IP address changes. So Tor will >>almost *never* change circuits in the middle of an IRC session. > > Despite your implied world expertise on these matters, I have > tested Tor FF and on several occasions found the exit node IP > address to change mid-way during a session when connected to > my own server. Not every time, but sometimes. > > Now, you were saying.....? the nodes have to change as the rate of traffic changes otherwise a node can get overwhelmed. regardless, it *ONION* routing with many peels. duh stoobie
From: hummingbird on 16 Jan 2010 16:41 On Sat, 16 Jan 2010 21:52:47 +0100 (CET), noauth wrote : > hummingbird wrote: > > > You've been forging my name for 18 months, > > You're confused. Hummingbird isn't your name, it's a nickname or > "nic", and YOU don't own it. It's my nick too.
From: za kAT on 16 Jan 2010 18:14 On Sat, 16 Jan 2010 23:03:16 +0000, hummingbird wrote: > 'za kAT' wrote thus: > >>On Sat, 16 Jan 2010 19:57:43 +0000, hummingbird wrote: >> >>> Despite your implied world expertise on these matters, I have >>> tested Tor FF and on several occasions found the exit node IP >>> address to change mid-way during a session when connected to >>> my own server. Not every time, but sometimes. >> >>I thought you didn't log IP's? > > Only yours :-) Have you ever seen this phrase: > > "_____ Go Away! - s-o-c-i-a-l-i-s-t-s not welcome. ROTFL _____" > > > [cue Stubbo: "no, never"] You're a hoot hum. -- za kAT
From: za kAT on 16 Jan 2010 18:16 On Sat, 16 Jan 2010 22:55:33 +0000, hummingbird wrote: > 'za kAT' wrote thus: >>"Do it now, before you forget." > > > http://preview.xrl.in/49k6 What's that then? Picture of you drooling? -- za kAT
From: »Q« on 16 Jan 2010 18:55
In <news:ba640e5fcd1bd4ccb134647b76d0caeb(a)aracari.org>, hummingbird <hummingbírd(a)127.0.0.1> wrote: > 'JB' wrote thus: > > >Actually, hummingbird is a bit confused on this point also. A > >collection of Tor nodes is called a "circuit". Tor functions by > >building these circuits and then routing information along them. > >Circuits don't "change during a session", they're changed according > >to certain rules. Some circuits are more "durable" than others, and > >in point of fact, Tor specifically leans toward *not* changing > >circuits in the middle of a session because when you do things like > >that you tend to really screw up communications between hosts. > > > >One of the exceptions to the "don't change" rule is simple HTTP. > >Web browsing normally isn't broken by an IP that's a moving target. > >Web servers are basically "dumb" machines, just sitting there > >spitting out packets to whatever requests that come in regardless > >of where they came from. > > > >Other protocols aren't so tolerant. IRC servers for instance will > >almost invariably boot you if your IP address changes. So Tor will > >almost *never* change circuits in the middle of an IRC session. > > Despite your implied world expertise on these matters, I have > tested Tor FF and on several occasions found the exit node IP > address to change mid-way during a session when connected to > my own server. Not every time, but sometimes. It's not clear what you mean by "Tor FF", but how often tor will build new circuits, &c., depends on how you've configured Tor. It's covered pretty clearly in the Tor manual page. If you've downloaded a Tor that's preconfigured only for web browsing, it's likely that new circuits are built periodically; as JB said, that rarely hurts web browsing. OTOH, if a circuit breaks, such as when a relay drops out, Tor has no choice but to build a new circuit, which might be what you're seeing. If you want to see how your Tor is handling things, just read the manual and your torrc. If you want to discard old circuits and force building of a new one, you can send a command to the running Tor. If you're using Vidalia to control Tor, there's a button to do that, labeled something a bit silly like "get new identity" IIRC. > Now, you were saying.....? Everything JB said in the quoted text above is correct. |