Linux

53416 readers

615 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Comprehensive guide to hardening RHEL clones? (lemmy.dbzer0.com)

submitted 6 days ago by marauding_gibberish142@lemmy.dbzer0.com to c/linux@lemmy.ml

24 comments fedilink hide all child comments

Is there some sort of comprehensive guide on hardening RHEL clones like Alma and Rocky?

I have read Madaidan's blog, and I plan to go through CIS policies, Alma and Rocky documentation and other general stuff like KSPP, musl, LibreSSL, hardened_malloc etc.

But I feel like this is not enough and I will likely face problems that I cannot solve. Instead of trying to reinvent the wheel by myself, I thought I'd ask if anyone has done this before so I can use their guide as a baseline. Maybe there's a community guide on hardening either of these two? I'd contribute to its maintenance if there is one.

Thanks.

you are viewing a single comment's thread
view the rest of the comments

[–] pastermil@sh.itjust.works 1 points 6 days ago

That narrows it down a lot. To be honest, I'm not familiar with that. However, with that specific of a topic, it shouldn't be that hard to look up for articles to follow and come up with a course of action.

The reason why OSes aren't 'hardened' by default is because it would be a real pain for users trying to set things up or use it for daily operation. If you take it to an extreme, they wouldn't be able to access anything they want. If you're a sysadmin, you'd be faced with your whole office pissed off because they wouldn't be able to do their work.

Last but not least, what does 'hardened' mean anyway? You can have something as 'hardened' as an airgapped workstation in a faraday cage with an off-grid power supply. Are you running away from a government agency? I wouldn't think so. So a firewall blocking unused ports and mindful practice should suffice.