Hello!
My name is Mansur. And I'm working on degree work about TOR network security.
I've seen that there's patch to Wireshark that gives you ability to
watch TOR protocol passing through Wireshark.
In fact, I have a problem compiling Wireshark with that patch -
there're some errors during
Andrew Lewman wrote:
On 01/29/2010 08:20 PM, 7v5w7go9ub0o wrote:
As we slowly transition to web 2.0, probably the next step is
putting the TOR browser in a VM full of bogus, randomized
userid/sysid/network information - carefully firewalled to allow
TOR access only (TOR would be running
I've been running an exit relay for about 6 months on my Linode VPS. The
bandwidth on my hosting deal is capped at 200Gb per month, so my relay is
limited to 50k, bursting to 90k - that keeps it safely around 80% of my monthly
bandwidth allocation.
I was wondering if switching my service to
Exit relays are definitely the most useful (thanks for running one!).
However, it's preferable to have a fast relay for part of the month rather
than a slow relay always available so I'd suggest using AccountingMax rather
than RelayBandwidthRate/Burst to stay below your provider's cap. Cheers!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mike Perry @ 01/28/2010 02:04 PM:
After all, in normal operation, your history leaks one fuckload of a
lot of bits. And that's a technical term. Sensitive ones too, like
what diseases and genetic conditions you may have (via Google Health
url
If you have Vidalia.app containing tor 0.2.1.22, and you've also
installed Apple's Mac OS X Security Update 2010-001, you'll have
noticed that Apple made some errors in their TLS renegotiation.
Apple removed TLS renegotiation even for apps that both need TLS
renegotiation and do it safely. Apple
scar wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Mike Perry @ 01/28/2010 02:04 PM:
After all, in normal operation, your history leaks one fuckload of
a lot of bits. And that's a technical term. Sensitive ones too,
like what diseases and genetic conditions you may have (via
scar wrote:
Mike Perry @ 01/28/2010 02:04 PM:
After all, in normal operation, your history leaks one fuckload of
a lot of bits. And that's a technical term. Sensitive ones too,
like what diseases and genetic conditions you may have (via Google
Health url history, or Wikipedia url history).
On Sat, Jan 30, 2010 at 04:07:59PM -0700, rd...@river.com wrote 2.6K bytes in
72 lines about:
: If you have Vidalia.app containing tor 0.2.1.22, and you've also
: installed Apple's Mac OS X Security Update 2010-001, you'll have
: noticed that Apple made some errors in their TLS renegotiation.
Mike Perry wrote:
[]
The reason why Torbutton didn't opt for the same origin policy method
is because Tor exit nodes can impersonate any non-https origin they
choose, and query your history or store global cache identifiers
that way. It was basically all or nothing for us.
Ah.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
thanks for the suggestions, 7v5w7go9ub0o.
i also read through [1] and am trying out the LinkStatus add-on[2].
it seems to work, and is kind of useful in that it tells me in the
status bar the time i last visited a link.
1.
11 matches
Mail list logo
