ansible-role-security VS anaconda

My playbook is only doing some software installation (openzfs, ...) and some SSH configuration (something really similar to jeff geerling : https://github.com/geerlingguy/ansible-role-security ), and it works perfectly without the tasks where I create groups and add user to these groups.

I suggest these resources: - Some fundamentals: https://www.cyberciti.biz/tips/linux-security.html - One of the best imho ( exhaustive list ): https://github.com/imthenachoman/How-To-Secure-A-Linux-Server - Ansible playbook to harden security by Jeff Geerling: https://github.com/geerlingguy/ansible-role-security - OAWSP Check list ( targeted for web apps... and honestly a bit overkill ): https://github.com/0xRadi/OWASP-Web-Checklist

THAT all being said. Check out this: https://github.com/geerlingguy/ansible-role-security. YOu can see everything Jeff Does. My guy is a mad genious :).

Solid advice, most of it is now covered by GeerlingGuy's Security Ansible role (https://github.com/geerlingguy/ansible-role-security) and the Firewall one (https://github.com/geerlingguy/ansible-role-firewall).

yea, what jessel0l said (or vlan) plus you could use something like chroot or podman to separate privileges. Remember to set up fail2ban sane and easy starting point might be https://github.com/geerlingguy/ansible-role-security

I'm on Fedora right now and will probably be keeping that. But aiming to add several linux distros in a multi-boot setup (no Microsoft products involved). The other likely candidates include Nobara, Rocky, OpenSUSE, Alphine, Arch, and Void (haven't decided on which ones or how many yet). I would like to set this up as one big LUKS2 partition with a Btrfs filesystem and each OS organized into its own respective Btrfs subvolume. I'm currently using BIOS mode but planning to reinstall under UEFI. My assumption is that I will need to have multiple boot partitions for however many OSes I plan to go with (haven't done much on UEFI before so I am unclear if distros can "share" a boot partition - particularly Fedora/Nobara/Rocky bc Anaconda has a bug where it removes the boot partition for other Fedora installs).

Anaconda is the installer for Red Hat (and RHEL, and Fedora, and CentOS, and Rocky, and...) and has been forever, much longer than Conda has existed. It is the installer RH distros

It creates a luks volume and places LVM on it, and only adds a 15G root logical volume in LVM.

Anaconda is the name of Fedora's installer.

The issue is that Red Hat broke ISO support in this commit and of course, as a Red Hat derivative, CentOS 8 has the same issue.