Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split off between a privileged daemon and an unprivileged frontend #3

Open
ghost opened this issue May 6, 2015 · 3 comments
Open
Assignees

Comments

@ghost
Copy link

ghost commented May 6, 2015

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? )

@ghost
Copy link
Author

ghost commented May 6, 2015

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.

@KellerFuchs
Copy link
Member

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.

@KellerFuchs
Copy link
Member

Huge success!

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.

@KellerFuchs KellerFuchs changed the title Rewrite idea - Sudo-less mode Split off between a privileged daemon and an unprivileged frontend Nov 28, 2015
@KellerFuchs KellerFuchs self-assigned this Nov 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant