How schm1d/awesomearchlinux works
Base Installation (in the “base” directory)
2. Hardening Modules (in the “hardening” directory, with submodules for firewall, SSH hardening, and sysctl settings)
Main Components
• Base Installer Module:
• Contains scripts like archinstall.sh, chroot.sh, and secureBoot.sh.
• This module is responsible for automating disk partitioning, formatting, setting up full disk encryption with LVM on LUKS (and a special encrypted boot partition), and configuring secure boot through GRUB.
• Hardening Module:
• Subdivided into dedicated areas:
▪ Firehol: Scripts that manage iptables and firewall configuration (firehol.sh).
▪ SSH: Scripts to harden SSH configurations (ssh.sh, ssh_client.sh) plus accompanying documentation.
▪ Sysctl: Scripts that apply kernel parameter hardening (sysctl.sh).
• Utility Module:
• A collection of miscellaneous scripts used for additional security or customization tasks (e.g., configurations for auditd, vim/neovim, themes, zsh, etc.).
• External System and User Interaction:
Relationships and Interactions
• Base Module → Hardening Module:
• Hardening Module → Utility Module:
• Utility scripts can be seen as either supplementary or optional, providing additional adjustments after the base hardening.
• Internal Dependencies:
• Within the base scripts, illustrate that archinstall.sh initiates the overall installation; chroot.sh is used to run post-installation configurations in the installed environment; and secureBoot.sh configures GRUB along with boot encryption.
• The hardening section is modular – each folder (firehol, ssh, sysctl) represents an independent submodule that collectively contributes to comprehensive system security.
• Iterative Customization:
• That there is an element of configuration where the user is expected to modify variable settings depending on their system setup. This customization step is central and should be highlighted.
Architectural Patterns and Design Principles
• Modularity:
• Separation of concerns: base installation, system hardening, and utility customizations are kept in separate directories to allow independent modification.
• Sequential Flow:
• Customizability:
• Variables like DISK, USERNAME, TIMEZONE, etc., are defined by the user. Represent these as inputs to the overall process.
• Security Enhancements:
• Clearly label components that deal with encryption, bootloader hardening, authentication, firewalling, and system auditing.
Specific Technologies, Frameworks, and Tools
• Arch Linux – the target OS.
• Shell Scripting – used throughout the project.
• LUKS and LVM – for full disk encryption.
• GRUB – for bootloader configuration and secure boot.
• iptables/firehol, PAM, sysctl – for security hardening.
• NVIDIA drivers installation tailored for systems with NVIDIA GPUs.
Instructing the Principal Software Engineer
• Incorporate elements like input parameters (user-customizable variables) feeding into the Base Installation module.
• Process scripts (e.g., installation and hardening jobs)
• Configuration scripts/utilities
• Documentation or informational resources (like README files).