Powersaves download for chromebook install#
Powersaves download for chromebook full#

You will then install Alpine using the steps:įirst you need WiFi, to get it run do the command below but say no or skip the hard drive setup stuff: Then, install all the tools into memory ramdisk but not in the hard drive yet. Set it up as usual but don't let it touch your drive yet. cryptsetup has luks actions luksHeaderBackup and luksHeaderRestore to do this. If you plug in the USB key, it will restore back the header. When you pull out the USB key, it should erase the header but store it on the USB key atomically as in completely. This presents an opportunity to improve obfuscation. If you did deniable encryption incorrectly, it is possible to erase and restore the header. To gain credibility that we didn't really do the encryption, you have to wipe the +3 MiB region based on the number of key slots used or store the headers on an external device. For example, cryptsetup does leave a plaintext marking or some hints by default that it has been encrypted when using luks/luks2 mode if a detached header with option -header is not presented. Is the drive just random noise, broken, or is it really encrypted? The other reason is that it implies that everything is protected.īut there could be problems if not done right.

Powersaves download for chromebook full#

The full disk encryption provides sort of some plausible deniability or a valid alibi that you didn't encrypt it. There shouldn't be an entry for your facade bootloader to the encrypted drive. Deniable encryption requires you not put encrypted as an entry title to your bootloader. It also requires you not to brag about encryption or mention it because that is an invitation for the attacker to torture the victim. The keys should be stored using steganography where we dilute the randomness into the facade. To achieve this we use a facade and require no metadata fingerprints to expose or hint of encrypted or hidden containers or hint as in detect of existence of an encrypted disk. In this article we use the words plausible deniability interchangeably with deniable encryption. We try to present deniable encryption (Wikipedia) to avoid a rubberhose attack scenario. Just a reminder that all attacks are subjected to the Rubberhose Attack dilemma, you either give up your encryption keys or be tortured with a rubberhose with the possibly of death. Encrypted home on top of encrypted drive.Two factor authentication (physical object (USB key), mind).14.2 Adjusting the backlight dynamically.11 Install the bootloader in the USB thumb drive.10 Hacking mkinitfs to support cryptsetup with GPG keys.9 Next step: Full blown Alpine installation.8.6 Configuring OpenRC dmcrypt and setting up fstab.8.5.2 Improved method with plausible deniability.8.5.1 Original method with fdisk with no plausible deniability.8 Full disk encryption with with cryptsetup-luks volumes.5 Randomizing the drive with pseudorandom urandom entropy.