Introduction

This is my fork of easy-arch, a script made in order to boostrap a basic Arch Linux environment with snapshots and encryption by using a fully automated process.

This fork comes with various security improvements and fully working rollbacks with snapper. I do submit some of the changes here back to upstream as well.

How does it work?

1. Download an Arch Linux ISO from here
2. Flash the ISO onto an USB Flash Drive.
3. Boot the live environment.
4. Connect to the internet.
5. git clone https://github.com/tommytran732/Arch-Setup-Script/
6. cd Arch-Setup-Script
7. chmod u+x ./install.sh && ./install.sh
8. do arch-chroot /mnt and create your wheel user once the script is done. Remember to give the wheel group priviledges in visudo.
9. Blacklisted Firewire SBP2 (As recommended by https://www.ncsc.gov.uk/collection/end-user-device-security/platform-specific-guidance/ubuntu-18-04-lts)

Snapper behavior

The partition layout I use rallows us to replicate the behavior found in openSUSE 🦎

1. Snapper rollback works! You will no longer need to manually rollback from a live USB like you would with the @ and @home layout suggested in the Arch Wiki.f2fs-tools udftools
2. You can boot into a readonly snapshot! GDM and other services will start normally so you can get in and verify that everything works before rolling back.
3. Automatic snapshots on pacman install/update operations
4. /boot and /boot/efi are 2 seperate subvolumes which will not be rolled back with snapper.
5. For consistency with pacman's database, I deviate from SUSE's partition layout leave /usr/local/ and /opt as part of the snapshot. When you rollback, everything in those 2 directories rollback as well.
6. GRUB will boot into the default BTRFS snapshot set by snapper. Like on SUSE, your running system will always be a read-write snapshot in @/.snapshots/X/snapshot.

Changes to the original project

1. Encrypted /boot (This was previously present on EasyArch, but Tommaso changed his script to use LUKS2 and have unencrypted /boot. Personally I would not do this, since encrypting /boot is the only way to protect the initramfs from being tampered with. GRUB will only validate the kernel if Secure Boot is used, not the initramfs).
2. SUSE - like partition layout
3. Snapper snapshots & rollback
4. Default umask to 077
5. Firewalld is enabled by default
6. Minimally setup GNOME 40 with pipewire
7. Added more filesystem support (Since Disk Utility is a GNOME dependency and it supports exFAT, NTFS, F2FS and UDF, I added support for those out of the box to make the experience a bit better out of the box)
8. Randomize Mac Address and disable Connectivity Check for privacy

Why so many @var_xxx subvolumes?

Most of these subvolumes come from SUSE's partition layout prior to 2018, before they simply made @var its own subvolume. We cannot blindly do this however, since pacman stores its database in /var/lib/pacman/local, which needs to be excluded and rolled back accordingly to the rest of the system.

Other than that, /var/lib/gdm and /var/lib/AccountsService must have their own read-write subvolume in order to boot GNOME from a read only snapshot.

Why GNOME?

I only use GNOME and I know that I have to explicitly create a seperate a subvolume for /var/lib/gdm, /var/cache, /var/tmp and so on for a full desktop to boot from a read-only snapshot. I don't know how other desktop environments behave and which directories we need to create a seperate subvolume for. We will also change the partitioning scheme according to the DE selection as well, since it doesn't make any sense to create @var_lib_gdm on a KDE system. Any help with adding more DE options would be appreciated.

Partitions layout

Partition/Subvolume	Label	Mountpoint	Notes
1	ESP	/boot/efi	Unencrypted FAT32
2	@/.snapshots/X/snapshot	/	Encrypted BTRFS
3	@/boot	/boot/	Encrypted BTRFS (nodatacow)
4	@/root	/root	Encrypted BTRFS
5	@/home	/home	Encrypted BTRFS
6	@/.snapshots	/.snapshots	Encrypted BTRFS
7	@/srv	/srv	Encrypted BTRFS (nodatacow)
8	@/tmp	/tmp	Encrypted BTRFS (nodatacow)
9	@/var_log	/var/log	Encrypted BTRFS (nodatacow)
10	@/var_crash	/var/crash	Encrypted BTRFS (nodatacow)
11	@/var_cache	/var/cache	Encrypted BTRFS (nodatacow)
12	@/var_tmp	/var/tmp	Encrypted BTRFS (nodatacow)
13	@/var_spool	/var/spool	Encrypted BTRFS (nodatacow)
14	@/var_lib_gdm	/var/lib/gdm	Encrypted BTRFS
15	@/var_lib_AccountService	/var/lib/AccountsService	Encrypted BTRFS
16	@/var_lib_libvirt_images	/var/lib/libvirt/images	Encrypted BTRFS (nodatacow)

To do

1. Automate wheel user setup
2. Install yay and setup hardened_malloc & opensnitch
3. Reduce the number of password prompts
4. Automatic secure boot setup with your own keys (no, we are not using shim).
5. Optional Nvidia driver installation
6. Automatic zram setup