You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm proposing an idea for a new version of the hashbangctl program.
Multiple clients, one server.
Clients write to server, server interfaces with the system as root. Clients won't need sudo permissions.
Thoughts?
( lrvick also suggested to make hashbangctl upgrade it's runtime user level to root, thoughts on this too? )
The text was updated successfully, but these errors were encountered:
So, lrvick did raise some good points. A server would be a lot harder to manage at the moment than to just get the client running. I'll get to working on a "no-calling-sudo" mode later.
I'm currently poking at something like that.
A draft of the protocol between frontend & daemon is documented, and I will push my branch to GitHub once it is sufficiently far along.
Finally figured out how to get gevent, provisor and Unix SOCK_SEQPACKETS sockets to play along. Also worked out how to do the getsockopt(SO_PEERCRED) call to ask the kernel about the identity of the process at the other end of the pipe.
I'm proposing an idea for a new version of the hashbangctl program.
Multiple clients, one server.
Clients write to server, server interfaces with the system as root. Clients won't need sudo permissions.
Thoughts?
( lrvick also suggested to make hashbangctl upgrade it's runtime user level to root, thoughts on this too? )
The text was updated successfully, but these errors were encountered: