heads
cryptboot
heads | cryptboot | |
---|---|---|
31 | 5 | |
1,380 | 198 | |
0.9% | - | |
9.5 | 0.0 | |
6 days ago | 5 months ago | |
Makefile | Shell | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
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.
heads
-
Thinkpad W530 No GPU output
I downloaded the VGA ROM for my Thinkpad W530 for both the Intel IGPU and Nvidia Quadro K1000M using this and configured the build config to use them with the correct PCI ports (8086,0166 10de,0ffc). Everything works fine except the output for both the VGA and the mini DP port. Does anyone have any ideas of what I could be missing here?
-
Can i make full disk encryption more convenient or should i just use an encrypted home dir?
You may be interested in Heads, which is available on Purism laptops under the name PureBoot. Though this really needs a coreboot-capable machine, I think, and isn't something you can just add to your existing UEFI boot chain.
-
Getting LUKS, Btrfs, Hibernation and Swap file working in tandem
You don't need to encrypt anything to verify those images, you just need to sign them. See how Heads does this.
https://github.com/osresearch/heads
-
Live OS needs a new name, what should it be?
Unfortunately there is also the Heads secure firmware: https://osresearch.net/ as well. Otherwise my vote would go to Heads. Liive OS could be pretty hard to optimize in a search engine, they'll think it's misspelled. Could call it "Miles" and just never ack the reference...
- Heads: Minimal Linux that runs as coreboot payload to provide secure environment
-
Grub, Syslinux, or another bootloader?
Heads, https://osresearch.net/
-
verify secure flash
If you worried about malicious changes, there is the write lock protection feature in coreboot that prevents internal flashing. This would require you to flash externally whenever you want to update coreboot. If worried someone will also flash your BIOS externally, you may want to look into Heads
- Dedicated mini PC for Bitcoin transactions with no wifi? Most Raspberry Pi models have wifi and the zero 1.3 seems to have been discontinued
- Physical Key Computer Access
- Is TPM actually anti-consumer?
cryptboot
-
Setting up Secure Boot, but the wiki doesn't provide enough info I think
I just completely cheated by using cryptboot. Then it is as simple as cryptboot-efikeys create, then to enroll them into your eufi, cryptboot-efikeys enroll and finally to sign any efi executable (or any file), cryptboot-efikeys sign $FILE. There are other helper scripts, but I don't use them. Full documentation is on their GitHub: https://github.com/xmikos/cryptboot. Good luck!
- Authenticated Boot and Disk Encryption on Linux
-
Physical security tips & recommendations
Prevent evil maid by bringing your devices everywhere. Or you can just switch to GNU/Linux and add https://github.com/xmikos/cryptboot
-
Unencrypted boot partition risks
I think it was this one: https://github.com/xmikos/cryptboot
-
Cool new things on linux world for fresh installation and a bit of my usage different things.
Also, I am pretty sure that you can only have encrypted /boot if you use GRUB. The point of doing so is not really to make sure nobody reads it (there isn't anything interesting on /boot by default), but to make sure that nobody can tamper with it (ignoring the encryption vs authenticated encryption discussion). However, you still have to make sure nobody can tamper with GRUB itself. You might want to check out https://github.com/xmikos/cryptboot if this sounds interesting. Also, there are similar solutions that don't use encrypted /boot, for example booting from signed EFISTUBs, see https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface/Secure_Boot#Implementing_Secure_Boot. Also, I don't actually use this kind of setup personally (albeit I'd like to one day), and I am certainly not a security expert, so take this whole paragraph with a big grain of salt, and double check with somebody who actually knows what they are talking about.
What are some alternatives?
skulls - pre-built coreboot images and documentation on how to flash them for Thinkpad Laptops
sbctl - :computer: :lock: :key: Secure Boot key manager
1vyrain - LiveUSB Bootable exploit chain to unlock all features of xx30 ThinkPad machines. WiFi Whitelist, Advanced Menu, Overclocking.
dotfiles - :unicorn: My personal dotfiles
NanoPi-R4S-OpenWRT - OpenWrt Frimwares for FriendlyARM NanoPi R4S
safeboot - Scripts to slightly improve the security of the Linux boot process with UEFI Secure Boot and TPM support
sbupdate - Generate and sign kernel images for UEFI Secure Boot on Arch Linux
EMBA - EMBA - The firmware security analyzer
mortar - Framework to join Linux's physical security bricks.
tpm2-totp - Attest the trustworthiness of a device against a human using time-based one-time passwords