On 12/24/2014 8:29 AM, mikael wrote:
> Hi,
> I don't know what to do. Please help.
>
> I'm getting the following warnings in arm:
> 16:13:15 [WARN] Your server (MY_PUBLIC_IP:9030) has not managed to
> confirm that its DirPort is reachable. Please check your firewalls,
> ports, address, /etc/hosts
On 12/10/2014 4:52 PM, usprey wrote:
> I do not have a full understanding of how the DirAuth works, but how
> about an out of band verification process, to ensure the
> trustworthiness, for exit nodes specifically. This would minimize the
> hazzle for people who wishes to use trusted exit nodes, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/24/2014 4:09 PM, Libertas wrote:
> I thought I'd share an initial draft of doc/HARDENING. Please
> share any opinions or contributions you have. This was written in a
> little more than an hour, so it's still a work in progress.
> However, in the
On Tue, Nov 18, 2014 at 10:09:37AM -0500, Libertas wrote:
> Hi, everyone. Linked below is a list of relays that were live last night
> along with the SSH authentication methods they support:
[snip]
> Generally, it is far more secure to allow only public key auth.
Nobody has mentioned using single
On 10/12/2014 6:56 PM, subk...@riseup.net wrote:
> [cross-posted on tor-talk and tor-relays]
>
> i've found that the Tor GoodBadISPs list [1] is somewhat outdated on
> current hosts that allow Tor (exit) relays to be hosted. i'm trying to
> find a cheap host that allows exits to be operated from t
