Hi yurivict271. Iirc the 1.4.5 release had an issue where cookie authentication wouldn't work with a ControlSocket. This setup is pointless (cookie auth doesn't provide you anything a ControlSocket doesn't) but that aside this is already fixed in the git codebase.
I'd suggest dropping CookieAuthentication or switching to a ControlPort for now.
Cheers! -Damian
Trac: Component: - Select a component to nyx Resolution: N/Ato worksforme Status: new to closed
I am using ControlPort - UNIX domain socket.
Cookie provides the ability to log into any of many tor instances with the command line w/out the password.
Tor supports UNIX domain ControlSocket, and this should be supported by arm with cookie auth for the ease of use from shell. Otherwise, how am I going to login? Type password every time? Cookie is for this.
Ideally it should be a command line for this, no need for ~/.arm/armrc, because in case of many instances armrc is a trouble.
Trac: Resolution: worksforme toN/A Status: closed to reopened
arm -i /var/tmp/tor/ctrl:/var/tmp/tor/data/control_auth_cookie
... but actually you want the -s or --socket argument. Also, there's no need to have the auth cookie location (that'll just cause an error, and I'm unsure why you think that would be valid syntax).
What happens when you run the following with the git checkout?
arm from git doesn't have -s argument.
What's run_nyx?
Arm was renamed to nyx. If you're using the git repository and executing something called 'arm' then you're running the wrong thing ('arm' no longer exists in the git codebase)...
No problem, sorry about the confusion. The rename is presently moot for users since arm is the last release (1.4.5). I hope to have a new release at which point the name will take effect later this year.