-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've spoken today with someone who had to back off in running a relay
from home because his IP address was blocked from accessing a
financial institution website. Quite uncomfortable.
I have made a simple non-technical draft letter to educate the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/11/2014 1:46 AM, Michael Wolf wrote:
> On 6/10/2014 6:17 PM, grarpamp wrote:
>> " http://www.norse-corp.com/darklist.html
>>
>> The world's first comprehensive blacklist of the Internet's
>> highest risk IPs.
>
> "Why secure your server when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 4/23/2014 5:58 PM, Ted Jackson wrote:
> I would like to change to an US Ip address when I want to?
> possible?
>
You can set a static exit node in your torrc but that is not
recommended at all as it will have impact on your anonymity.
Always r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Reading the dev list yesterday I saw that a scan was performed on all
the relays in the Tor network and the ones vulnerable to OpenSSL
heartbleed had their fingerprints listed with a !reject argument by
the directory authorities.
So far so good
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
After seeing the challenge done by CloudFlare, to setup a server open
to the internet with that vulnerable OpenSSL version so everyone could
try and get its private keys (to see if it's actually possible), after
speaking earlier with people in #
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I have upgraded to latest Tor Browser Bundle version: 3.5.4 - Windows
32 bit.
My operating system is Windows 8.1 Pro Enterprise, 64 bit.
The odd things i have noticed (which didn't happen in previous
versions) are:
1. Some kind of cookie / se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Onions,
Reading the blog post with the DDoS possible attack to terminate
relays by making RAM memory scarce, I would like to ask the following:
In Tor versions > 2.4 a defense against these types of attacks was
deployed (MaxMemInCellQueues). MaxMe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
When a new version of Tor is released, one which makes significant
changes to routing rules, covers security vulnerabilities, etc. - how
do all the ~6000 relays upgrade to the latest version automatically
and simultaneously so the peers in the net