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
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...
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
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
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 Arisbe. Think I vaguely recall seeing a report about this before.
Nyx (aka arm) is undergoing a rewrite. Mind giving the new codebase a
whirl?
https://nyx.torproject.org/
Unfortunately there aren't any releases yet so you'll need to snag it
from git. Think the following should do the trick...
Hello people,
I'm not a python programmer so I need some help with a problem. I have a
number of Tor nodes and some bridges. Occasionally, when I install
tor_arm I get a divide by zero message as follows:
Exception in thread Thread-69: Traceback (most recent call last):
File
>> Is this ok or is it deprecated and I should install something else? And
>> how?
>
> It works well enough now and it is being improved slowly with a name change.
> (As far as I can tell.).
Yup, that is correct. I was hoping to have the next release out for
you by around this time but it's
Cristian,
> tor-arm
>
> Is this ok or is it deprecated and I should install something else? And
> how?
It works well enough now and it is being improved slowly with a name change.
(As far as I can tell.).
Robert
___
tor-relays mailing list
This package is usually running fine for me...
Le 16/06/2016 à 12:07, Cristian Consonni a écrit :
> 2016-06-16 3:00 GMT+02:00 grarpamp :
>> On 6/14/16, NotRandom Someone wrote:
>>> What do you think about using tor-arm ?
>>
2016-06-16 3:00 GMT+02:00 grarpamp :
> On 6/14/16, NotRandom Someone wrote:
>> What do you think about using tor-arm ?
>
> https://gitweb.torproject.org/nyx.git/
>
> Arm now known as Nyx.
On my node (running with Debian Jesse as OS) I have
Hi everyone,
I have a question about monitoring a tor middle relay.
What do you think about using tor-arm ?
Is it safe ? (Bugs, leaks,etc) ?
Or using just the informations on globe/atlas.torproject.org is more useful
?
Thank you.
___
tor-relays mailing
Thanks!
On Jan 29, 2016 1:08 AM, "Louie Cardone-Noott" wrote:
>
> If I've understood your question: press i and select 1 second, then
> enter.
>
> Press h for other keyboard options.
>
> On Fri, 29 Jan 2016, at 12:17 AM, SuperSluether wrote:
> > How would I change the
If I've understood your question: press i and select 1 second, then
enter.
Press h for other keyboard options.
On Fri, 29 Jan 2016, at 12:17 AM, SuperSluether wrote:
> How would I change the interval? Arm keeps telling me there's no armrc
> loaded, and to see the sample file for options, but
Not hurting anything and in general if you see a message that's
'notice' that means 'this is fine, just for your information'. If it
was a problem it would way it was a warning or error.
On Thu, Jan 28, 2016 at 10:29 AM, SuperSluether wrote:
> Ok, so just wait for arm to
When arm starts it attempts to read tor's state file to get past
bandwidth information. That is a notice level message, not an error,
and it's simply telling you that it wasn't able to prepopulate all the
data.
Tor has changed its state file format which actually breaks that
feature entirely. The
Found this error when checking my relay today:
ARM_NOTICE Read the last day of bandwidth history from the state file
(- seconds is missing)
Every time I start arm, the -xxx seconds missing is different. The
bandwidth graph is also stuck, but real-time data is still shown.
Is this a
Ok, so just wait for arm to get updated then? I guess as long as it's
not hurting anything, it doesn't matter too much.
On 01/28/2016 12:06 PM, Damian Johnson wrote:
When arm starts it attempts to read tor's state file to get past
bandwidth information. That is a notice level message, not an
What does the
cat /var/log/tor/log
says?
On Tuesday, June 17, 2014 6:56 PM, Adam Griffin adgri...@gmail.com wrote:
Running top in a separate SSH session shows ~50% load average. I imagine
spikes would cause the CLI interruptions and maybe relay unresponsive/resumed
notices. Did you have
Last 'log' entry was from a few days ago when I started it. Just shows
bootstrapping 0-100% without errors.
'notices.log' entries happen fairly regularly. Mostly heartbeat uptime
notifications and lifetime sent/received. Also bugging me to add my
ContactInfo. No errors relating to tor-arm's odd
Hi,
Just started a new tor relay on my raspberry pi yesterday and I'm
monitoring with tor-arm over ssh. I'm currently listed on
atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid'
with 17hrs uptime.
However, tor-arm is showing a blank for uptime and about once a minute, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Had the same issues on my pi when running over ssh.
It simply is the fact, that your pi is running almost on max load. Type top in
your console, and watch the pi working :)
On 17. Juni 2014 19:28:23 MESZ, Adam Griffin adgri...@gmail.com wrote:
Hi,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Yes, especially when hitting Enter after sudo -u debian-tor arm
Then it took a few seconds and the relay resumed.
It never seemed to have these problems when running on it's own, so I think
this is just due to the limited resources of the pi
Running top in a separate SSH session shows ~50% load average. I imagine
spikes would cause the CLI interruptions and maybe relay
unresponsive/resumed notices. Did you have the same blank uptime issue?
On Tue, Jun 17, 2014 at 2:08 PM, Elrippo elri...@elrippoisland.net wrote:
-BEGIN PGP
24 matches
Mail list logo