Hello all, running Debian 12 right now and really liking this thing. I never ran straight Debian before, always mint or Ubuntu. But anyway…
I’m wondering if you guys could recommend some troubleshooting or scanning tools that help you find errors, misconfiguration, basically any thing that could be wrong with your system. I’d much prefer GUI tools as CLI tools can be a bit confusing.
So my only thoughts are auditing type apps. Don’t those comb through your system for issues? I’ve tried Lynis and it seemed pretty cool, need to explore further. Of course you got your vulnerability scanners which I plan to use. You’ve got your rootkit scanners and clamv for malware. I just got netdata up and running last night. Now that is one confusing ass app lol so many options and i dont really kniw what im looking at lol. But I’m more interested in the system itself. I know I have some issues within my system. Htop only tells you so much and it never answers my problems when my computer random freezes or It starts overworking and heating, yet no high CPU or memory usage showing on htop.
I know I have networking issues with my VPN and DNS and other stuff. I just lack the knowledge to know where to look and what to fix, so trying to finder more user friendly, maybe more proactive tools I can use to help me discover things within the system that need attention. Overall I just want a healthy, dependable, safe, secure Linux system and I always endupFrankensteining my shit just trying different crap and everything eventually falls apart lol so help with some reomendations please, folks!
Personally, I find Ansible to be much more intuitive than other products in the configuration management space. Start small, think about what you want your system to look like.
Do you want Firefox installed? Use ansible.builtin.package to install it!
Do you want to have ssh server configured to disallow password authentication (and only allow ssh keys)? Use ansible.builtin.blockinfile on your sshd.config file!
Regarding SELinux vs apparmor, they both are designed to lock down a system, but they have different philosophies about how to approach the problem.
SELinux says block all by default and only if it’s configured to allow it will it be allowed to happen.
Apparmor on the other hand is permissive by default, and it will only restrict if it is configured to do so.
By the way, both can be managed by Ansible, and SELinux even has a module to do so: https://docs.ansible.com/ansible/latest/collections/ansible/posix/selinux_module.html.
Fascinating stuff! A tad confusing lol but definitely learnable. So to me, selinux and app armor sound similar to firewalls… On the surface at least
I suppose you could say it’s similar in that there are allow-lists and deny-lists that permit or restrict actions, but the key difference is Apparmor/SELinux are in the OS space - they can permit/restrict the ability to restart services, or prevent sudo from being used in certain ways.
Firewalls are predominantly used to permit/restrict network connectivity either ingress (e.g. traffic from outside the system coming into it) or egress (e.g. traffic that is leaving the system). A good example would be using a firewall to restrict ingress traffic to port 22 - allowing remote management of a system over SSH.
I hope this is helpful!
Thanks!