-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Post-installation encryption #22
Comments
Glad to hear you're finding it useful! You can indeed encrypt the chroot after it's been created--just run crouton again with the same parameters you used to create the chroot, but with -u (update) and -e (encrypt). It will make you create a root password in Chromium OS if you haven't already, and then it will ask you for an encryption password and encrypt the chroot. |
Awesome. Thank you very much for the detailed explanation! |
David. Please specify the full parameter to -e (encrypt) a chroot. Rather than just saying "use same parameters as used to create the chroot", please just spell it out for us numb-sculls. |
The full parameter to -e (encrypt) is simply -e
Take a look at the crouton usage display below for the '-e' option and many others.
Hope this helps, |
@ssyyddii |
Hi, I recently started using Crouton and I love it! It lets me get a ton of use out of my Chromebook. Thanks for writing it!
When I initially installed my Ubuntu chroot I did it without encryption (mainly just to see if it would work at all). Now that I've spent some time setting up my dev environment, I'm realizing I should probably encrypt the chroot directory. Is this possible? Or does that need to be done at install-time?
Thanks again for making such a great tool!
The text was updated successfully, but these errors were encountered: