On 01.09.2017 21:26, Damian Johnson wrote:
> Nyx (aka arm) is undergoing a rewrite. Mind giving the new codebase
> a whirl?
I had a look, and I am wondering if there is any way to specify the
controller password in ~/.nyx/config ? It is supported in arm, via
the startup.controlPassword option in
HI Ralph. I dropped that since it posed a security issue. When using
password authentication nyx provides a prompt, then drop the reference
so the memory can be released (if someone knows a better way of
purging a password from memory in python I'm all ears).
I'd suggest cookie authentication if y
On 02.09.17 21:26, Damian Johnson wrote:
> I dropped that since it posed a security issue.
Sigh... That seems a bit overzealous to me.
> I'd suggest cookie authentication if you'd care to rely on file
> permissions rather than something you know. That'll work transparently.
I don't think I unde
>> I'd suggest cookie authentication if you'd care to rely on file
>> permissions rather than something you know. That'll work transparently.
>
> I don't think I understand what exactly you are suggesting. Could you
> provide an example?
The ControlPort supports none, password-based and cookie-b
On 02.09.17 23:39, nusenu wrote:
> The ControlPort supports none, password-based and cookie-based
> authentication, Damian was suggesting the cookie option:
>
> https://www.torproject.org/docs/tor-manual.html.en#CookieAuthentication
> https://www.torproject.org/docs/tor-manual.html.en#ControlPort
On Sun, Sep 03, 2017 at 01:17:14AM +0200, Ralph Seichter wrote:
> I also tried using a control socket instead of a control port, alas, the
> parameter RelaxDirModeCheck is rejected by Tor 0.3.0.10:
>
> [warn] Failed to parse/validate config: Unknown option
> 'RelaxDirModeCheck'. Failing.
> [
Hi Ralph, I think there's some confusion about the ssh verses tor
password. All I'm suggesting is that instead of
'HashedControlPassword' you use 'CookieAuthentication 1' in your torrc
instead. This is discussed a bit on the following in case you'd care
to read more...
https://stem.torproject.org/
Oops, sorry - my bad. Didn't spot that this was already answered under
a different email subject. :)
On Sat, Sep 2, 2017 at 6:27 PM, Damian Johnson wrote:
> Hi Ralph, I think there's some confusion about the ssh verses tor
> password. All I'm suggesting is that instead of
> 'HashedControlPasswor
On Sat, Aug 26, 2017 at 6:38 AM, Paul Templeton wrote:
>> If you're interested in becoming your own ISP (obtaining your own ASN,
>> IPv6 and IPv4 scopes), you'll need to apply via APNIC, as I did in the
>> US with ARIN.
>
> Would if I could - but here in AU you have to log all metadata for two yea
Could you please define “Metadata”? Server connections? That would be quite a
bit with a high traffic tor relay …
niftybunny
“For too long, we have been a passively tolerant society, saying to our
citizens 'as long as you obey the law, we will leave you alone'”
--David Cameron, 2015
> On 26
> If you're a subscriber of such an ISP, it's turtles, such ISP has same
> data as
> you would anyways, thus this irrelavant. Only way to evade is with an
> anti-GPA
> network analysis design which tor doesn't and won't provide.
>
Wondering what an anti-GPA network analysis is...
> Could you please define âMetadataâ? Server connections? That would be
> quite a bit with a high traffic tor relay â¦
>
> niftybunny
>
Generally speaking I believe metadata is source IP, Source port,
Destination IP, Destination port, timestamp of connections.
For the USA government and othe
These days, layer 3 IP is nothing other than handy identifier
for layer 2 and below traffic characterization and probing.
So long as everyone continues whining about bandwidth, which
can perhaps be mostly free at link layer, or are being anti-mix,
as starter defenses... they'll get no solution. IMO
13 matches
Mail list logo
