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

Add descriptions why sudo is needed for each step it's needed #20

Closed
oberien opened this issue Jan 23, 2017 · 1 comment
Closed

Add descriptions why sudo is needed for each step it's needed #20

oberien opened this issue Jan 23, 2017 · 1 comment

Comments

@oberien
Copy link
Collaborator

oberien commented Jan 23, 2017

No description provided.

@main--
Copy link
Owner

main-- commented Jan 24, 2017

Dunno. It should be obvious for most, shouldn't it? Like how else do you expect us to edit your root-owned 644 /etc/mkinitcpio.conf? Magic?

And sure, printing sudo commands so you don't have to fully trust us makes sense in theory - but you gain nothing. Not only can we just fake the whole thing, we could also simply run our payload after any sudo command as we then have a session. Or, you know, abuse the fact that we can already install files and run code as root. Either we modify your system for you and you trust us to do the right thing or you do it yourself entirely - there is no middle ground (compare: self-xss).

@oberien oberien mentioned this issue Jun 9, 2017
@main-- main-- closed this as completed Jul 9, 2017
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

2 participants