Sorry, I mean this in light of CVE-2014-0160 the Heartbleed OpenSSL bug
On Wed, Apr 9, 2014 at 11:04 AM, lee colleton l...@colleton.net wrote:
I have relay(s) running in AWS. Will they auto-update? Do I need to take
any action?
___
tor-relays
HTTP-without-porn should be called BurkaHTTP. I'm sure there's a backronym
that will fit…
On Aug 28, 2013 4:15 AM, mick m...@rlogin.net wrote:
On Tue, 27 Aug 2013 19:34:13 -0700
Andy Isaacson a...@hexapodia.org allegedly wrote:
If only there were a separate TCP port for HTTP-with-Porn and
here's that email again in plain text (previously held for moderation
due to message size)
On Thu, Aug 22, 2013 at 3:13 AM, lee colleton l...@colleton.net wrote:
here's both netstat - tulpen and netstat -tulpen
lee@tor-bootstrap:~$ netstat - tulpen
Active Internet connections (w/o servers
CA names sent
---
SSL handshake has read 7 bytes and written 225 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
---
On Thu, Aug 15, 2013 at 10:14 AM, lee colleton l...@colleton.net wrote:
-tor-relay
+tor-relays
On Thu, Aug
-tor-relay
+tor-relays
On Thu, Aug 15, 2013 at 10:13 AM, lee colleton l...@colleton.net wrote:
All of the ports respond on the external IP except for 443 but I can
connect via SSL on 9001. I don't understand how ORListenAddress is
supposed to work: my bridge times out on 443 but when I
