levinboot
cryptsetup-nuke
levinboot | cryptsetup-nuke | |
---|---|---|
3 | 2 | |
- | 17 | |
- | - | |
- | 0.0 | |
- | over 3 years ago | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
levinboot
-
PinePhone Pro was announced last week. AMA.
The RK3399 LPDDR4 training code is open-source (albeit rather impenetrable to read) - implementations exist in coreboot, u-boot, and levinboot, so closed source firmware isn't required. I'm afraid I don't know answers to the other questions.
- Fedora on the PinePhone: Pipewire Calling
cryptsetup-nuke
-
Plausibly Deniable Encryption
There's always LUKS to cover this scenario: Nuke Keys that get activated with a second password. [1]
[1] https://github.com/roema/cryptsetup-nuke
-
PinePhone Pro was announced last week. AMA.
Easily. You can use https://github.com/roema/cryptsetup-nuke to do it at boot time, you can use an evil-maid tool to detect and wipe luks at init-time if the boot partition was tampered with, and just cryptsetup erase /dev/...; echo b > /proc/sysrq-trigger to wipe the luks header and immediately force a hard reboot
What are some alternatives?
u-boot - "Das U-Boot" Source Tree
bitlocker-spi-toolkit - Tools for decoding TPM SPI transaction and extracting the BitLocker key from them.
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.
pineeye_for_pinephone - Thermal imaging board aimed to be used with the PinePhone.
Jumpdrive - Flash/Rescue SD Card image for PinePhone and PineTab. This is NOT a bootloader
coreboot - Mirror of https://review.coreboot.org/coreboot.git. We don't handle Pull Requests.
glodroid_manifest - Android port that aims to bring both user- and developer-friendly experience in using AOSP with a set of single-board computers (SBC), phones and other devices.