On 11/22/2017 10:01 AM, Chris Laprise wrote:
Glad you recovered OK. The best way to execute the vm-sudo instructions is to switch to root user first with 'sudo su'. Notice that all the shell prompts in the document are '[root@vmname]#'.
BTW I have a project Qubes-VM-hardening that uses vm-sudo configuration to leverage template-based security. Its an added layer of protection against malware persistence.
The master branch currently only deals with user init scripts, but the systemd branch has some more interesting things in development, like white-listing.
https://github.com/tasket/Qubes-VM-hardening -- Chris Laprise, [email protected] https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/881ca94d-5ad9-23f2-5516-40dfa2a5de65%40posteo.net. For more options, visit https://groups.google.com/d/optout.
