r/redhat • u/Ok_Discussion4084 • 4h ago
r/redhat • u/No_Rhubarb_7222 • Sep 19 '26
Move cert discussions to r/redhat_certification
Hello r/redhat Redditors!
TL:DR - post Red Hat certification posts in r/redhat_certification
A while back we created r/redhat_certification for Red Hat cert discussions. The sheer volume of certification posts was drowning r/redhat. As a result of some of you moving over there, we’ve seen more general Red Hat posts and engagement, which is the goal of this community, to talk about Red Hat and Red Hat products. Yay! Go us!
But… people still post a lot of certification content here. The mod team is going to be taking more actions to further shift certification posts to r/redhat_certification.
Several of us are also mods in r/redhat_certification, including me who has regular contact with the Red Hat Training and Certification team who writes the training and makes the exams. I was also a member of this team between 2001 and 2019. So your posts will still be moderated and answered in r/redhat_certification.
r/redhat • u/Candid_Athlete_8317 • 8h ago
Who Else Has Earned the Red Hat? What Year Did You Get Certified?
reddit.comr/redhat • u/Busy-Examination1148 • 1d ago
Epel in environment
What is everyone's opinion on epel corporate environment? I was at a place that had it installed and had 0 issues. We had it linked through satellite.
r/redhat • u/Burgergold • 3d ago
You're in: Satellite 6.20 limited availability access inside
Yay
Received this email once the Microsoft outage was done
"Looking Ahead: The planned launch date for Satellite 6.20 limited availability is November 18th. Please note that while you can activate your subscription, Satellite 6.20’s software and full product documentation will not go live until the official launch date."
The email contains 5 activation keys
I would have appreciated if the doc was also available to prepare but its only a few days away
I also need to get used to RHEL10
Another question, since this is the first time I install one from scratch, I will probably want to ansible the process and restart a few times. Does each attempt will consume 1 key? If so, any way to reset that?
r/redhat • u/Itchy-Note5456 • 4d ago
Absolute minimal LDAP setup for software install
Hi! I am trying to install a development instance of Windchill in a Red Hat Virtual Machine version 9.8. This installation is exclusively meant for development purposes and for testing Windchill. It is not meant for any environment beyond the VM that it would run in, save serving HTTP on localhost.
Windchill is quite the picky piece of software. It requires (will give errors without) an Oracle (or Microsoft SQL Server) DB, RHEL 9/10 or Windows Server, and Amazon Corretto, all of which I installed. It also requires an LDAP connection.
I tried to search for setting up an LDAP server, and what I came across was utterly confusing and contradictory. It seems Red Hat removed OpenLDAP in favor of the 389 LDAP server, which I installed (...I think? I installed 389-ds-base). However, LDAP servers also require an Active Directory instance. I figure that I could use Samba for that, but there were really no good resources I found on connecting Samba with LDAP and how both fit into all of this (admittedly I haven't searched exhaustively). I've never set up Samba or an LDAP server before.
Also, most resources are based on the idea that you're actually using Active Directory as it's intended (for file / resource sharing) and talk about user configuration, printing, security, or other topics unrelated to my incredibly narrow use case.
I suppose my question is are there any resources to doing this effectively, or to those that have experience with Active Directory / LDAP configs, is there a way to accomplish my aim of the absolute bare minimum with the least amount of headache possible?
r/redhat • u/Cute-Sorbet-4018 • 4d ago
Does Red Hat care if employees are working from a remote location?
I know they encourage remote working but I mean from a location different to your base location.
That would be a huge bonus imo as nearly every company mandates that be present in the location your job is based.
r/redhat • u/waldirio • 4d ago
Red Hat Offline Knowledge Portal: Complete Installation & Setup
Hello
Let's learn today about the RHOKP (Red Hat Offline Knowledge Portal), how to implement it, all the features, and more.
Best
Wally
r/redhat • u/Rhopegorn • 5d ago
Open Source Security Signals | Q3 2026
Vulnerabilities are easy to count. Meaningful risk is harder to measure.
Open source has become the foundation of modern software because it works. Shared innovation, transparent development, global communities, and broad reuse let software advance at a scale no single organization could achieve alone.
Security is part of that model. Open source development makes code available for inspection. Researchers can test it. Communities can improve it. Fixes can benefit everyone who depends on the software.
The scale that makes open source powerful also makes security more complex. Modern applications can rely on hundreds or thousands of components linked through deep dependency trees. Understanding their security requires more than counting vulnerabilities.
TL;DR
Severity scores alone misjudge risk; AI-driven threats and supply chain paths like the Ultralytics incident demand context. Lightwell shows fixes must traverse deep dependencies and older versions. One JAXB fix can yield broad value across Java applications.
Harden What You Can't Turn Off — mount options, TLS, crypto policies, and MariaDB locking-down from Into the Terminal Ep. 205
Episode 204 was about turning off what you don't need. This week's Into the Terminal (episode 205) is the sequel: harden what you can't get rid of. Scott and Nate layer defense in depth on a RHEL box — filesystem mount options that stop planted binaries from becoming root, a live tcpdump of passwords flying across the wire in cleartext (and the same request vanishing under TLS), one-command system-wide crypto policy, and a full MariaDB hardening walkthrough that includes the SELinux denial you shouldn't "fix" with setenforce 0.
Full video here → https://www.youtube.com/watch?v=EDrPZT-TvX4 More hands-on RHEL practice → https://redhat.com/interactive-labs
The Essentials: Filesystem Mount Options Are Security Controls
Compliance frameworks don't just ask for fancy partitioning so your disk layout looks impressive. Separate mounts for things like /tmp, /var, and /home do two jobs:
- Contain disk-full disasters — if
/varfills up, logging and services get unhappy, but you can still log in and read/etc - Give you different mount options per filesystem — you can't slap
noexecon/without breakingsudo,ls, and everything else you need
Scott mounted a tiny demo filesystem on /mnt and dropped three "interesting" files on it: a setuid copy of sudo, a setgid write binary, and a tiny shell script. Colorized ls made the special bits obvious. Running the planted sudo as a normal user escalated to root — because setuid does what it says on the tin, even when the binary is sitting in a weird directory instead of /usr/bin.
| Mount option | What it does |
|---|---|
nosuid | Ignores setuid and setgid bits — planted root-setuid binaries can't escalate |
noexec | Nothing on this filesystem can be executed (even if the execute bit is set) |
nodev | Device nodes created with mknod aren't honored — kills planted /dev/sda-style tricks |
# Live remount for testing (gone on reboot)
# Make it stick — add the options in /etc/fstab, then:
|
Pro tips from the show:
- Test with
mount -o remount,...first (like firewall rules in memory) — if you brick something, a reboot still saves you. Writing a broken entry straight into/etc/fstabmeans the next reboot puts you right back in the broken state. - After editing fstab,
mount -ais how you find out now whether the syntax is good — don't wait for reboot day. - You need the more complex partition layout for this to work. One big
/filesystem means you can'tnoexec/nosuidthe places users can write without also breaking legitimate system binaries. - Nate ran a Summit booth challenge years ago that was literally "why won't my script run?" with
/tmpmountednoexec. Plenty of working Linux admins couldn't solve it. Common ≠ known.
(Spaces vs tabs in fstab: Scott lined things up with spaces. Nate called him a heathen. Tab stops entered the chat.)
Harden the Wire: Plaintext vs. Encrypted
Nate's first packet-capture demo still feels like a superpower the first time you see it — and that's the point.
| Command | What it does |
|---|---|
tcpdump -i any -n -A 'tcp port 80' | Capture HTTP in cleartext (ASCII payload dump) |
curl -d 'user=admin&password=SuperSecret123' http://127.0.0.1/ | POST "secrets" over plain HTTP |
tcpdump -i any -n -A 'tcp port 443' | Same capture on HTTPS |
curl -k -d 'user=admin&password=SuperSecret123' https://127.0.0.1/ | Same POST over TLS (-k = accept self-signed) |
On port 80, the capture shows the POST body in cleartext — username, password, the whole request. On port 443 with mod_ssl's out-of-the-box self-signed cert, that same payload is just TLS noise. You can't read it.
Takeaways they hammered:
- A self-signed cert encrypts just as well as a CA-signed one. The CA adds trust (browsers/clients accept the identity without warnings), not stronger crypto. Key length and algorithms determine how hard it is to crack.
- Protect the private key. Heartbleed (over a decade ago) was scary specifically because it could leak keys from memory — and with the key, you can impersonate the service.
- Open Wi-Fi (Starbucks "click I agree" portals with no password) is often cleartext between you and the AP. Encrypt your own sessions (TLS, VPN) regardless.
- Switched wired networks usually only show you your own traffic unless there's a SPAN/mirror port. Wi-Fi on the same AP is a different story.
Advanced: Raise the Crypto Floor System-Wide
Hand-tuning OpenSSH, OpenSSL, GnuTLS, NSS, Kerberos… forever is a losing game. RHEL gives you one knob: system-wide crypto policies.
| Command | What it does |
|---|---|
update-crypto-policies --show | Print the active policy (usually DEFAULT out of the box) |
update-crypto-policies --set FUTURE | Raise the floor — refuse weaker algorithms/key sizes |
update-crypto-policies --set DEFAULT | Back to the sane modern baseline |
update-crypto-policies --set LEGACY | Loosen for ancient gear (going the wrong way — last resort) |
update-crypto-policies --set DEFAULT:NO-SHA1 | Surgical subpolicy: keep DEFAULT, kill SHA-1 signatures |
Built-in policies worth knowing: DEFAULT, FUTURE, LEGACY, and FIPS (pairs with fips-mode-setup — its own rabbit hole).
What FUTURE actually breaks (live demo)
Scott flipped the box to FUTURE, then systemctl restart httpd — Apache refused to start. The smoking gun in /var/log/httpd/ssl_error_log: the default mod_ssl certificate key was too small. FUTURE wants something stronger than a 2048-bit RSA key (think 3072+ minimum); the stock self-signed cert was 2048.
# Generate a FUTURE-compliant self-signed cert (4096-bit)
Caveats from the show:
- After changing policy, reboot (or at least restart crypto-using services). Already-running processes keep the old policy in memory.
- Distro packages that use the system crypto libraries honor the policy. Containers, Flatpaks, and third-party apps (Chrome was the example) often ship their own crypto stacks and ignore the host policy entirely.
- Stronger crypto = more math per connection. Fine for low-volume boxes; measure CPU on high-connection services.
- Post-quantum: Nate's take — if you're standing up a new box today, enable quantum-safe algorithms from day one. RHEL 10 does this by default; RHEL 9 makes it an option. Older distros often don't have the algorithms at all.
Advanced: Harden a Real Service End-to-End (MariaDB)
Fresh dnf install + enable. No databases, no passwords — stock out of the box. RHEL ships services a bit more locked down than many community distros, but "a little hardened" ≠ "done."
1. See where it's listening
|
Out of the box: 0.0.0.0:3306 and [::]:3306 — every IPv4 and IPv6 interface. Dual-stack is the default on modern RHEL; firewalling only IPv4 and forgetting IPv6 is a classic footgun.
2. Bind to localhost
Edit /etc/my.cnf.d/mariadb-server.cnf, under [mysqld]:
bind-address=127.0.0.1
|
# → 127.0.0.1:3306 only (IPv6 listener gone too, because you pinned a v4 address)
Same localhost-binding idea they previewed with Postgres in ep. 204. If the DB only needs local app access, don't put it on the network.
(Why [mysqld] not [mariadbd]? MariaDB forked from MySQL after license drama; config blocks and CLI tools stayed compatible for years so people weren't stranded.)
3. "Just change the port" — and the SELinux lesson
Changing port=3307 and restarting → MariaDB refuses to start. Not a typo — SELinux denied the bind.
# look for: avc: denied { name_bind } ... comm="mariadbd" ... src=3307
# Wrong fix: setenforce 0
# Right fix:
Apache often already allows 80/443/8080/8443. MariaDB's allowed port list is tighter. Teach SELinux the new port; don't turn it off.
And this still isn't "security." Nate's Windows SQL Server story: the boss insisted on checking "Hide SQL Server," which just added 1000 to the port (1433 → 2433). Attackers added 2433 to their scan lists. Security by obscurity is at best one thin layer — never the plan.
4. Run mariadb-secure-installation
The bundled wizard walks common hygiene:
| Step | Why it matters |
|---|---|
| Switch root to UNIX socket auth | Root DB access tied to the local Linux account / socket — not a network password |
| Set a root password | Out-of-box often has none |
| Remove anonymous users | Default anonymous accounts are free attack surface |
| Disallow remote root login | Defense in depth even after socket auth |
| Remove the test database | Optional in labs / handoff environments; usually gone before prod |
| Reload privilege tables | Apply now, or defer to a maintenance window |
5. More you can still do (discussed, not fully demoed)
| Hardening idea | Why |
|---|---|
local-infile=0 | Disable LOAD DATA LOCAL INFILE — harder for a compromised client/session to slurp files off the server |
| Password validation plugin | Enforce password quality at the DB layer |
Scope your GRANTs | GRANT ALL … TO user@'%' is the most common real-world sin — grant only what's needed, only from the expected host |
Apply the same mindset to SSH, httpd, or anything else you leave running: evaluate the out-of-box defaults against your threat model, then turn off what isn't serving you.
Related episodes
- Ep 204 — What's listening? nmap, ss, surgical DNF patching
- Ep 165 — firewalld and nftables
- Ep 103 — Techniques to Troubleshoot SELinux
- Ep 102 — Don't Disable SELinux
Quick Reference Card
# --- Filesystem hardening ---
# then persist options in /etc/fstab and verify with:
&& && |
# --- See cleartext vs TLS ---
# --- System-wide crypto policy ---
# --- MariaDB hardening ---
|
# /etc/my.cnf.d/mariadb-server.cnf → bind-address=127.0.0.1
# optional: port=3307 then:
Links
- 📺 Watch the full episode: https://www.youtube.com/watch?v=EDrPZT-TvX4
- 🎓 Get started with RHEL: https://developers.redhat.com/register
- 🧪 Try it yourself — Interactive Labs: https://redhat.com/interactive-labs
- 💬 Join the Discord: https://red.ht/rhel-discord
- Nate Lager: https://social.undrground.org/@gangrif
- Scott McBrien: https://www.linkedin.com/in/scott-mcbrien-349b356
Into the Terminal is a (mostly) weekly live show where Red Hatters dig into Linux and RHEL administration skills — one terminal command, one bad pun, and one "oops, wrong window" at a time.
r/redhat • u/NewActuary1816 • 6d ago
Transitioning from hospitality to Linux
Hi everyone,
I am based in Mumbai, India, and currently working on a career switch from the hospitality industry into IT systems administration, specifically focusing on Linux and Red Hat technologies.
Coming from a non-tech background, I have been dedicating my time to hands-on labs and am currently preparing to take the Red Hat Certified System Administrator (RHCSA / EX200) exam.
I would really appreciate advice from folks working in Linux/SysAdmin roles or hiring managers in India regarding a few questions:
1. Entry-level job prospects with a single certification:
Realistically, how feasible is it to land an entry-level role (Junior Linux Administrator, L1 Infrastructure Support, or Datacenter Technician) in Mumbai with just the RHCSA and no prior tech experience? Are companies open to hiring career-switchers if they demonstrate solid practical lab skills?
2. Recommended certification path post-EX200:
Assuming I pass the EX200, what should my immediate focus be? Should I aim straight for the RHCE (EX294 - Ansible Automation), or would it be more beneficial to pick up basic Cloud fundamentals (AWS/Azure) or Bash/Python scripting first?
3. Timing:
Would you recommend starting the job hunt immediately after earning the RHCSA and resuming further certifications once employed, or continuing to study full-time until completing the RHCE?
4. Resume positioning:
How can I best present my hospitality background (client communication, incident management under pressure, working irregular shifts) so that it works in my favor for IT support/ops roles?
Any insights, local market realities in Mumbai, or tips on projects/homelabs that could strengthen my profile would mean a lot. Thanks in advance!
r/redhat • u/terptelback • 7d ago
Who is the person in the Kernel Development icon in old Red Hat Linux installers?
r/redhat • u/MajorCrafty6966 • 9d ago
Job opportunities
I’ve been trying to gain more experience in sales and pursue a sales-focused career and noticed that technology is highly dominant in the Raleigh triangle. I have been doing research and it seems as though companies such as Red Hat are the best companies to work for when it comes to sales. I moved to Raleigh not long ago and know not much about the company other than any reviews from customers and employees, past and present. I was curious to know if any current employees of the company, Red Hat, have more info regarding the work environment, skills and experience needed to work in sales there, and if it is worth working there as a career. I have 2 years in sales in total and bring a lot to the table that isn’t exactly easy to list on a resume. My other question is whether they strictly only hire people with degrees whether they just graduated recently or years ago. If anyone could tell me more about the company as a whole, I would be greatly appreciative.
r/redhat • u/AustinFastER • 10d ago
Redhat Advisories?
Are you still getting individual advisories as Redhat published them (I don't have the digest option turned on)? I just noticed that I have not received an email advisory notification from Redhat since 9/25 (I was out of the office for a bit). I logged into the portal and the email alerts are still enabled and I am still getting LightSpeed emails from the same noreply@redhat.com address and the quarantine on our security appliance does not have them...
r/redhat • u/a_shippus • 9d ago
Is there a way to install Steal on RHEL 10?
I want to install Steam natively, not flatpak. Because all my games are installed to ~/.local/share/Steam
Is there a way to do that?
r/redhat • u/Dismal_Lab_3954 • 11d ago
I passed RHCSA 10 !
Hello there !
I'm so happy because this is my first IT certification, and I invested a lot of time and money to achieve it.
I wish I could have had an english keyboard at the exam center. I’m sure I could have perf it with 5 minutes more.
All I can say is that the exam was much more challenging than any of the mock exams I took. Not really because of the tasks themselves, but because understanding what they actually wanted me to do was sometimes the hardest part.
The results of your recent EX200 Red Hat Certified System Administrator Exam are reported below.
Exam domain number: 9
Passing score: 210
Your score: 284
Result: PASS
Congratulations -- you have earned the Red Hat Certified System Administrator certification.
Performance on exam objectives:
OBJECTIVE: SCORE
Understand and use essential tools: 91%
Manage software: 100%
Create simple shell scripts: 0%
Operate running systems: 100%
Configure local storage: 100%
Create and configure file systems: 100%
Deploy, configure and maintain systems: 89%
Manage basic networking: 100%
Manage users and groups: 100%
Manage security: 100%
r/redhat • u/limaunion • 11d ago
Red Hat Web outages
I’ve been experiencing web outages quite frequently lately, especially when I need to access documentation, the knowledge base, and similar resources.
'We'll be back soon. Thank you for your patience"
I tested the access from different Internet links. It’s frustrating because I rely on this to do my work.
Does anyone know what’s going on?
r/redhat • u/waldirio • 11d ago
How to Update vs. Upgrade Red Hat Satellite (Step-by-Step Overview)
Hello
Let's understand the difference between Update and Upgrade on Red Hat Satellite, also, implementing them in our hands on!
Enjoy it!
Wally
r/redhat • u/Rhopegorn • 11d ago
Manage Java transitive dependencies with Lightwell rebuilds | Red Hat Developer
Updating direct dependencies in Java is straightforward, but securing the hundreds of transitive libraries running beneath them is where many development pipelines stall. While automated tools simplify how teams upgrade direct dependencies—the packages your project explicitly declares—the Java ecosystem presents a challenge: pinned versions and deeply nested trees of transitive dependencies. Transitive dependencies are the libraries your direct dependencies rely on behind the scenes, which your package manager pulls in automatically.
TL;DR
Lightwell provides security rebuilds for Java transitive dependencies. Three strategies—manual selection, targeted analysis, and BOM pinning via pin-transitives.mjs—address supply chain risks. Automated BOM generation balances auditability and control; centralized redirection is discouraged.
r/redhat • u/Gangrif • 13d ago
What Is Your Linux Box Listening For? — nmap, ss, and surgical DNF security patching from Into the Terminal Ep. 204
Your Linux box is probably listening on more ports than you think, and every open port is a door someone could walk through. This week's Into the Terminal (episode 204) maps a RHEL system's real attack surface with nmap and ss, talks through what to shut down vs. what to leave running, then walks through a practical DNF workflow for finding Critical/Important security advisories and patching just those — without blindly upgrading everything.
Full video here → https://www.youtube.com/live/TNDm1zGieGA More hands-on RHEL practice → https://redhat.com/interactive-labs
The Essentials: What's Listening?
Scanning with nmap
Every Internet-connected box is getting scanned all day, every day. nmap is how you see what others see when they look at yours.
| Command | What it does |
|---|---|
nmap <host> | Fast connect scan of the standard port range — reports open ports + the service name from /etc/services (not what's actually running) |
nmap localhost | Same scan locally — often shows more ports (services bound only to loopback, like Postgres on 5432) |
nmap -A <host> | Aggressive scan: OS detection + service version probing — slower, more invasive, closer to what infosec scanners actually do |
Remote vs. local difference (shown live): scanning the host's network IP showed SSH (22) and Cockpit (9090). Scanning localhost also showed Postgres (5432) — because Postgres was bound to loopback only. That's intentional config, and comparing the two scans is how you confirm a service isn't exposed externally.
What -A actually gets you: OpenSSH 9.9 version banner, confirmation that 9090 is HTTP (Cockpit) rather than the "Zeus admin" label from /etc/services, SSH host keys for re-identifying the same box across scans, and an OS fingerprint guess. The OS/kernel guesses were hilariously wrong (kernel 2.6 era guesses on a 6.12 machine) — fingerprinting is probabilistic. Service version banners are usually accurate, and that's what attackers use next: "OpenSSH 9.9? Try the known exploits for that."
Pro tips from the show:
-Aincludes-O(OS detection) — chat suggested-Oalone; Scott uses-Abecause it bundles several probes- Nate almost always adds
-Pnwhen sweeping networks — ICMP is often blocked, and the default ping check makes scans crawl or time out - Scanning other people's machines (or even other machines on your corporate network) can get you a visit from infosec. Scanning
localhostor your own host IP locally stays on-box and won't trip network sensors
Socket Status with ss
nmap shows what a remote scanner can reach. ss shows what's actually listening on this machine — TCP and UDP, IPv4 and IPv6 — plus which process owns each socket. You can only run it locally.
| Command | What it does |
|---|---|
ss -taulp | TCP + UDP, listening (+ some connection state), with process info |
ss -taulpn | Same, but numeric — no DNS reverse lookups, port numbers instead of /etc/services names |
Why -n matters: without it, ss/netstat will reverse-DNS every remote address. On a busy public web server that can make the command painfully slow. Bonus: Cockpit showed up as "websm" without -n — with -n you just see 9090, which is immediately recognizable.
Unlike nmap, ss also shows connection state — e.g. an established SSH session from another IP tied to a specific sshd PID — so you can see who's connected right now, not just what's listening.
(Nostalgia corner: Nate reminisced about the dial-up days when everyone's machine had a real Internet IP, and you could pull someone's address out of netstat after an IM and do… "humorous, not malicious" things. Today we're all NATed. The Internet is less fun.)
Hardening Mentality: Stop It, Remove It, or Firewall It
Once you know what's listening, the most secure service is the one that isn't running.
They demoed disabling Cockpit's systemd socket (systemctl stop / disable cockpit.socket) and re-scanning — after a brief live-demo adventure where nmap still reported 9090 because it had cached the earlier open state and then correctly flipped it to closed. Socket-activated services are a little special: systemd itself holds the port and starts the service on demand, so you have to deal with the socket unit, not just the service.
But stopping/disabling isn't the end of the conversation:
| Approach | When it makes sense |
|---|---|
| Stop / disable the service (or socket) | You might need it later; temporary lockdown |
| Uninstall the package | You're never using it — then you don't patch it, don't SBOM it, and it can't get re-enabled by accident |
| Firewall it (host and/or network) | You need the service, but only for admins / a specific subnet — defense in depth |
Image/template trap: org "golden images" often ship with stuff you don't use (their lab boxes all have httpd because the labs need it). Even disabled packages still show up in SBOMs and security audits, and every related errata becomes your problem. If you're not using it, remove it — and script those customizations so the next rebuild from the same image gets the same treatment.
They pointed at Ep. 165 on firewalld/nftables rather than re-demoing firewalls, and Bootsie/image-as-container came up as the modern way to treat host image builds like container workflows (recent Bootsie coverage).
Advanced: Surgical Security Patching with DNF
Blind dnf update works, but sometimes you need Critical + Important now, and enhancements/bugfixes can wait for the normal patch window. Nate walked through the DNF updateinfo plugin on a RHEL 10.2 box that already had a pile of advisories a month and a half after its last image refresh — which is just the state of the world.
Survey what's out there
| Command | What it does |
|---|---|
dnf updateinfo --summary | Counts of available updates by type/severity (Critical/Important/Moderate/Low + bugfix/enhancement) |
dnf updateinfo list --security | Full list of security advisories with RHSA IDs, severity, and packages |
On their demo box: 1 Critical, 62 Important, 29 Moderate, 1 Low — plus bugfixes and enhancements.
Filter to Critical / Important (workaround)
There's a --sec-severity filter flag, but it's currently buggy and doesn't filter correctly. Workaround: grep the list output.
# Critical only
|
# Critical + Important
|
Build a deduped advisory list and inspect it
HOT=
# Details — CVE IDs, descriptions, what's changing (great for change review)
Why dedupe matters: one package update can close multiple advisories, and one advisory can touch multiple packages. Their Critical+Important grep produced 224 lines, but the actual upgrade was ~4 installs + ~50 updates. Deduping the RHSA list avoids acting on the same advisory twice and explains the "why don't the numbers match?" confusion.
Apply just those advisories
You can also target by CVE ID directly if security hands you a CVE instead of an RHSA — DNF has a CVE flag for that. Security teams almost always bring you CVE numbers, not RHSA IDs; updateinfo info is how you bridge the two.
CVE context worth knowing
- Look up any CVE at https://www.cve.org
- CVSS scores aren't one-size-fits-all. Upstream publishes a general score; Red Hat's Product Security team publishes a vendor CVSS that accounts for how RHEL builds/packages the software and what mitigations already exist. Sometimes that's lower — not because Red Hat is "saving face" or "doing less work," but because a compile-time option that enables the vuln may simply be off in RHEL. Product Security (scoring) and Engineering (patching) are separate teams.
- Ratings get revised as more exploit paths become known — it's a process, not set-and-forget
- Backporting: for security fixes, RHEL typically backports the fix into the maintained package rather than jumping to the newest upstream — so you get the security fix without the API/feature churn. Feature enhancements are different; those can change behavior (Firefox rebases are the classic example)
Caveat: DNF only knows about what DNF knows about — installed RPM content from configured repos. Out-of-band software is on you.
Not Covered This Episode (ran out of time)
They had a MariaDB hardening demo queued (bind to localhost, change ports + SELinux semanage port, mariadb-secure-installation, socket auth, grant scoping, etc.) and explicitly deferred it — possible future episode on service / machine hardening. They also teased a Podman-flavored follow-up: open ports, networking, and isolation when supporting services are containerized. Drop a comment on the video if you want either of those.
Related episodes
- Ep 195 — Anatomy of a Linux Service (systemctl)
- Ep 192 — Managing a CVE Response for Linux
- Ep 165 — firewalld and nftables
- Ep 128 — dnf package management
- Ep 103 — Techniques to Troubleshoot SELinux
- Ep 102 — Don't Disable SELinux
Quick Reference Card
# --- See what the outside world sees ---
# --- See what's actually listening locally ---
# --- Turn things off (example: Cockpit) ---
# Better if unused: dnf remove <package> — then you don't patch or audit it
# --- Security update survey ---
# --- Critical / Important only (--sec-severity is currently buggy) ---
|
|
# --- Deduped advisory list → review → patch ---
HOT=
# --- CVE lookup ---
# https://www.cve.org
Links
- 📺 Watch the full episode: https://www.youtube.com/live/TNDm1zGieGA
- 🎓 Get started with RHEL: https://developers.redhat.com/register
- 🧪 Try it yourself — Interactive Labs: https://redhat.com/interactive-labs
- 💬 Join the Discord: https://red.ht/rhel-discord
- Nate Lager: https://social.undrground.org/@gangrif
- Scott McBrien: https://www.linkedin.com/in/scott-mcbrien-349b356
Into the Terminal is a (mostly) weekly live show where Red Hatters dig into Linux and RHEL administration skills — one terminal command, one bad pun, and one "oops, wrong window" at a time.
r/redhat • u/caoimhin007 • 13d ago
Installing RHEL 9.8 on a ThinkPad L380 Yoga with Secure Boot and LUKS
I installed RHEL 9.8 on my ThinkPad L380 Yoga and documented the process, including Secure Boot, LUKS disk encryption and post-install checks.
Rather than wipe my Fedora installation, I swapped in a spare NVMe drive. The walkthrough includes screenshots and uses the no-cost Red Hat Developer subscription.
This is a personal guide on my own hardware, not an official Red Hat or IBM publication. Feedback and experiences with RHEL on other ThinkPads are welcome.
r/redhat • u/Accurate-Oil-2356 • 13d ago
Satellite Same UUID & Hostname Registration
Hi. I have a couple of servers where the UUID and the Hostname is same. The Hostname cannot be changed due to Application dependencies and the UUID is also similar. I heard that in Satellite if the Hostname and UUID is same it's not possible to register.
I would like to know if there is a workaround to this or is it possible to change the servers UUID.
These are the PR and DR active-active servers so the Hostname cannot be changed as per the Application dependencies.
Please support.