sbupdate VS ohmyzsh

I use sbupdate [0] to build the unified kernel image and to sign it with my keys. It's run by a hook in the arch's package manager whenever the kernel, the initrd or the firmware images change. I saw the other day that systemd recently got an utility to do this, but I've never looked into that. sbupdate has been working fine for me for several years now.

It doesn't store a new key in the uefi, it signs the new image with the key that uefi already knows about.

See [1] for the whole setup and [2] for the signing part specifically.

[0] https://github.com/andreyv/sbupdate

[1] https://wiki.archlinux.org/title/Unified_Extensible_Firmware...

[2] https://wiki.archlinux.org/title/Unified_Extensible_Firmware...

Here is where different systems will fork. On Arch there is a pacakge sbupdate where it automatically generate unified kernel images using pacman hooks and I use systemd-boot (which must be signed by your keys) to load it.

I really think it's easy enough. You create your keys, put them into /etc/efi-keys, enroll them into your UEFI by whatever method you prefer, install sbupdate-git and you're done... You need to run sbupdate manually once after install, everything else works automatically through hooks.

Ah, sbupdate does that very well; it embeds the kernel image, initramfs and the UEFI boot image into a unified signed image. I presume this signed image should then be further encrypted?

Check out https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface/Secure_Boot and https://github.com/andreyv/sbupdate

For the last part, check out https://github.com/andreyv/sbupdate . Linked also from arch wiki, so not some completely random solution. Its for creating unified kernel images, including the initramfs, microcode and so on. This package is then signed for secureboot, and can be loaded using EFISTUB for example. This prevents attacks against initramfs or some other things on /boot, if unencrypted. I haven't come around to test it myself, but I think its a neat solution, and with proper secure boot (and password protected firmware), a reasonable protection against evil maid attacks.

I am using secure boot with custom keys, a fully encrypted root btrfs partition with /boot on it, with swap also encrypted with hibernation support. The only non-encrypted partition is the EFI partition with boot images signed with https://github.com/andreyv/sbupdate (look up "direct booting").

If you are not using oh-my-zsh, you are missing out on some amazing plugins. One feature most people wish the terminal had is autocompletion. With the zsh-autosuggestions plugin, your terminal will autocomplete most commands and remember previous ones.

That’s the minimum terminal setup. You can modify the look and add plugins such as autocompletion to your terminal by installing ohmyzsh and using themes such as powerlevel10k. I am already using them.

Somewhat related is "Oh My ZSH!" which is basically zsh on steroids, it's always one of the first things I install on a new computer. It gives things like new colors, themes, plugins, and more. Highly recommend you check it out.

https://ohmyz.sh/

I had just gone through a fun tutorial for setting up oh-my-zsh with a nice color scheme from iterm2colorschemes.com and a decent prompt and I was wondering: can I make my oblique strategy look nice? how can you actually use the colors from your scheme in the output in your cli?

After this you going to visit Oh-My-Zsh which is where the magic will happen.

after automating my dotfiles, I want to automate my installations, after that I want to make my terminal easier to use so I add OMZ with many plugins, after that, I try to automate the backup of my setting on my Gnome but failed, then try using git-lfs for my big files but it turned out to be idiotic moves, bla bla bla many try and fail.