-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks. I saw the OpenSSL update, but thanks for explaining what it was about.
Is it necessary to restart Tor to apply the update?
Jesse V.
On 06/06/2014 04:00 AM, tor-relays-requ...@lists.torproject.org wrote:
Message: 1
Date: Thu, 05 Jun
On Fri, Jun 6, 2014 at 11:04 AM, Jesse Victors
jvict...@jessevictors.com wrote:
Thanks. I saw the OpenSSL update, but thanks for explaining what it was about.
Is it necessary to restart Tor to apply the update?
Yes. Any time the Tor binary or its libraries are updated, a restart
is required.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ok, will do, thanks.
On 06/06/2014 07:10 AM, Tom van der Woerdt wrote:
Yes, please restart Tor after updating
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
I've signed up to AWS with Tor's instructions for bridges. I've intalled
Tor on my PC. Wondering how to proceed. Am obviously an illiterate newbie,
so any links for a basic knowledge-base would be greatly appreciated.
Thanks in advance.
___
tor-relays
On Fri, Jun 6, 2014 at 6:05 PM, CD bajayaday...@gmail.com wrote:
I've signed up to AWS with Tor's instructions for bridges. I've intalled Tor
on my PC. Wondering how to proceed. Am obviously an illiterate newbie, so
any links for a basic knowledge-base would be greatly appreciated. Thanks in
I want to contribute to Tor, maybe I mean relay? That's why they suggested
the easiest way was thru AWS. So I got an account that's free, sort of.
Thanks for replying.
On Fri, Jun 6, 2014 at 12:35 PM, Runa A. Sandvik runa.sand...@gmail.com
wrote:
On Fri, Jun 6, 2014 at 6:05 PM, CD
You don't need tor installed on your local machine to contribute to the
Tor network by running a AWS-based relay.
Did you spin up an AWS EC2 micro instance using the image on
cloud.torproject.org? If so, then (at least in principle) you don't need
to do anything more, but it's probably a good
Hi All,
FP! :)
I just setup my relay node today, and am keeping a hawkish(ish) eye on
traffic And noticed a flurry of activity from SSH port (22) at
5.104.224.5 - which is listed as an exit.
But it's also listed on http://cbl.abuseat.org/lookup.cgi?ip=5.104.224.5
as infected (or