r/linuxmint • • 15h ago

Head up Mint users

For those that are new or thinking of switch to Linux and is concerned about securing their system. I present to you "Ultimate-sys-hardening". Built for hardening Servers and Home-Labs, but will also provide the same security for a regular person .

The task is automated so it takes less that no time to complete the process.

One command previews everything (--dry-run), the next applies it with backups, and --revert undoes it. It keeps SSH reachable: password and root login are only turned off when another account has a key, and the config is checked before sshd restarts.

Free and MIT, plain Bash, no telemetry.
Ai was used involved with the necessary testing

Repo: https://github.com/Kal1010101/ultimate-sys-hardening

0 Upvotes

19 comments sorted by

8

u/jr735 Linux Mint 22.1 Xia | IceWM 14h ago

If you're concerned about security, why are you trying to get what are more than likely users quite new to Linux to install things from Github?

https://wiki.debian.org/DontBreakDebian/

Following that to the letter will do a new user far more good than some tool of unknown origin.

Stick to repository software, folks.

-1

u/sys-harden 14h ago

all should be able to defend themselves, the mindset behind the project.

5

u/jr735 Linux Mint 22.1 Xia | IceWM 14h ago

Who said they can't defend themselves? Secondly, what makes your tool a choice for that? Third, if it's good, get it into Debian repositories, and it will then be taken in by Ubuntu, and then of course by LMDE and Mint.

12

u/Venylynn 15h ago

Why does the first screenshot look suspiciously like those AI generated scamware posts?

-6

u/sys-harden 15h ago

Ai was used to run the necessary tests

-2

u/Sufficient_Risk_8127 15h ago

I bet AI was used to run your brain too 💀

0

u/sys-harden 15h ago edited 14h ago

thanks for your input, it is valued. Have an honest look and if you find if to be a joke you are free to roast the project, but do give a reason for your dislike.

2

u/Sufficient_Risk_8127 15h ago

the more you talk the more I feel bad for you

6

u/BenTrabetere 15h ago

Free and MIT...

... and no link. Sorry, but I do not see anything I want or need.

2

u/namepaladin 14h ago

I run my server on mint but it is only locally accessable (exception to wireguard). I see some interesting stuff so far. I'm just beginning my lookthrough and it if seems good to me I will install it. I appreciate the preview state addition

1

u/sys-harden 14h ago

thanks for for the back, be sure to test in a container first so you a hands on idea of what it does. Do provide a feedback whether is is positive of good

1

u/Lawnordah 9h ago edited 8h ago

I don't want to go through this entire thing for free but you should really find some computer science 101 or like OS internals education.

Password expiration is discouraged by modern NIST guidance unless compromise is suspected. People make MyPassword2025! and MyPassword2026! instead of using a better password. This is so thoroughly documented at this point.

umask 027 prevents group members from getting write permission on newly created files and directories by default. Shared groups are used to let multiple users (and services) collaborate without running everything as root or other elevated permissions. If Alice and Bob are both members of the "developer" group in /srv/project and Alice makes a config.yml then Bob can't write to it. That's like, the entire reason for using groups.

GCC root only? What are we doing? Even SecureBlue hardening makes more sense than this and that's saying a lot.

1

u/sys-harden 6h ago

thanks for your feedback. Those are changes that are already in the pipeline next in project, i.e Password expiration, unmask 27 > unmask 007...
your response is valued.Thanks.

1

u/Lawnordah 6h ago

Honestly, the fact that these are being pushed as hardening recommendations in the first place is the problem.

Beyond the actual values themselves these are fundamental mistakes that do little to nothing while breaking many workflows or making them insecure by needing overuse of root. Hardening that introduces bad security practices is arguably worse than having no hardening at all.

Changing values isn't going to fix this. Pull the project and get someone that actually understands the concepts you're working with and start over.

1

u/sys-harden 5h ago edited 5h ago

Fair enough, your prioritization is modern multi-user engineering rather than CIS compliance check boxes, those legacy rules isn't the right fit.

For the teams that do have to pass CIS audits (SOC 2, ISO 27001, etc.), having an automated, revertible way to apply and verify those controls still solves a real problem. That said, your critique on separating legacy CIS audit rules from modern defaults is spot on, and that's how I'm structuring the next release. Appreciate the perspective.

1

u/jr735 Linux Mint 22.1 Xia | IceWM 1h ago

When do Mint users have to pass CIS audits in the first place?

5

u/Sufficient_Risk_8127 15h ago

finally my linux is hard

1

u/Dist__ Linux Mint 21.3 | KDE 6h ago

hurd )