r/redhat • u/Professional_Tip7692 • 1h ago
OCP/RH-Operators on OKD
r/redhat • u/cerbereag • 3h ago
About a month ago I asked here if a tool to see ps, ss or lsof output at a past moment was worth building:
https://www.reddit.com/r/redhat/comments/1wyzyeu/im_thinking_in_building_a_linux_time_travel_tool/
I got some fair pushback (sar, atop, below, Prometheus, zabbix) and a few people who were curious. I looked at all of them. They cover a lot, but none of them could tell me which process had which connections open, or what lsof showed for a process at 02:45 last night. So I built it, mostly to find out if it could be done without hurting the server.
I wanted to name it "command line time travel" but then a though about the consequences of such a name and It's called clifr instead (command line flight recorder) and has two parts:
clifrd runs as a service and records processes, process starts and exits (through eBPF, so a process that lives 5 ms still shows up), TCP connections with the process that owns them, files held open, mounts, kernel messages and the usual system counters. It keeps 72 hours in /var/lib/clifr, 2 GB max.
clifr rebuilds the output of the normal commands for a past moment or a time range. It doesn't run the command, it rebuilds the output from the recording.clifr --at "02:45" "ps aux" clifr --since "02:00" --until "03:00" "ss -tanp dst 10.0.4.21 and dport = :5432" clifr --since "1 hour ago" events # starts, exits, OOM kills, mounts clifr diff --at "14:00" --at "14:20" "ss -ltnp"
There are about 40 commands so far: ps, top, pidstat, lsof, ss, netstat, free, vmstat, iostat, mpstat, df, ip, dmesg, systemctl list-units, lsblk, and more and all are 100% accurate.
The first thing people asked last time was the cost, so here are the numbers:
| Quiet server | Mixed load | Busy server | |
|---|---|---|---|
| CPU | 0.35% of one core | 0.5-0.6% of one core | 1.9% of one core |
| RAM | ~90 MiB | ~80-120 MiB | ~290 MiB (335 max) |
| Disk | ~`20 MiB/day | ~100 MiB/day | ~4 GiB/day |
| Network | none, no ports open | none | none |
Disk use depends heavily on how busy the server is.
clifr is not a monitoring tool and has no alerts. It's not a security audit tool either: it doesn't record file reads or writes, and root can stop it. It's for the "what was going on at 02:45" question, after the fact.
Status: it's a prototype, version 0.1.0. It hasn't run on a real production server yet (a friend starts one this week), and all the load has been synthetic. AGPL-3.0, no telemetry, nothing leaves the box.
So if you have a test or dev box (RHEL 8/9, Rocky, Alma), I'd really appreciate it if you tried it and told me what breaks or what looks wrong. The most useful thing for me is comparing what clifr shows with what you know was really happening.
curl -LO https://github.com/jlruedab/clifr/releases/download/v0.1.0/clifrd-0.1.0-1.x86_64.rpm
curl -LO https://github.com/jlruedab/clifr/releases/download/v0.1.0/clifr-0.1.0-1.x86_64.rpm
sudo dnf install ./clifrd-0.1.0-1.x86_64.rpm ./clifr-0.1.0-1.x86_64.rpm
sudo systemctl enable --now clifrd
# wait a few minutes, then:
clifr --at "5 minutes ago" "ps aux"Repo, with an install guide, a user guide with use cases, and all the benchmark numbers:
https://github.com/jlruedab/clifr
And thanks to everyone who commented on the first post, including the harsh ones. It made this better.
r/redhat • u/idunnofrr • 10h ago
So yeah, i will use RHEL for DD(daily drive), is gaming something possible on it?
r/redhat • u/FewTree4863 • 13h ago
I wrote a small read-only health checker for Linux hosts (Python standard
library only, no dependencies, no daemon). It is tested on Debian 13, Ubuntu
26.04.1 and Fedora 45, but not on the RHEL family, and I would rather ask than
guess.
It prints one report for load/memory/swap/temperature, disk and inode usage,
failed systemd units, Docker, md RAID, SMART, backup age, TLS expiry and NTP,
then exits 0/1/2/3 for cron. Nothing is written to the host.
On RHEL-family systems I am unsure about a few things:
- Is systemctl --failed still the right signal, or do you watch something else?
- Do checks around subscription-manager make sense, e.g. pending errata or
unfixed security advisories?
- Is firewalld state useful in a one-command check, or just noise?
- Is there anything SELinux-related a read-only tool should surface?
If you run RHEL, Rocky or Alma, what would you actually want in a one-command
health check? I am not claiming RHEL support yet; I want to know whether it is
worth adding.
I've tested it on Fedora45-Debain13-Ubuntu.26.04.1 LTS
Repo: https://github.com/jacoblockard2007-hub/labcheck (MIT, 0.1.0)
r/redhat • u/Candid_Athlete_8317 • 2d ago
r/redhat • u/Busy-Examination1148 • 3d ago
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 • 4d ago
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 • 5d ago
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 • 5d ago
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 • 6d ago
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 • 6d ago
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.
r/redhat • u/NewActuary1816 • 8d ago
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!
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
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 /var fills 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 noexec on / without breaking sudo, 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)
mount -o remount,nosuid /mnt
mount -o remount,noexec /mnt
mount -o remount,nosuid,nodev,noexec /mnt
# Make it stick — add the options in /etc/fstab, then:
umount /mnt
mount -a # re-read fstab and attach everything
mount | grep /mnt # confirm the options stuckPro 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/fstab means the next reboot puts you right back in the broken state.
After editing fstab, mount -a is 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't noexec/nosuid the 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 /tmp mounted noexec. 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.)
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.
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).
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)
openssl req -x509 -nodes -days 365 -newkey rsa:4096 \
-keyout /etc/pki/tls/private/localhost.key \
-out /etc/pki/tls/certs/localhost.crt \
-subj "/CN=$(hostname)"
systemctl restart httpd # now starts under FUTURECaveats 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.
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."
ss -tulnp | grep 3306Out 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.
Edit /etc/my.cnf.d/mariadb-server.cnf, under [mysqld]:
bind-address=127.0.0.1systemctl restart mariadb
ss -tulnp | grep 3306
# → 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.)
Changing port=3307 and restarting → MariaDB refuses to start. Not a typo — SELinux denied the bind.
sudo ausearch -m avc -ts recent
# look for: avc: denied { name_bind } ... comm="mariadbd" ... src=3307
# Wrong fix: setenforce 0
# Right fix:
sudo semanage port -a -t mysqld_port_t -p tcp 3307
systemctl restart mariadbApache 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.
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 |
| 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.
# --- Filesystem hardening ---
mount -o remount,nosuid,nodev,noexec /mnt
# then persist options in /etc/fstab and verify with:
umount /mnt && mount -a && mount | grep /mnt
# --- See cleartext vs TLS ---
tcpdump -i any -n -A 'tcp port 80'
curl -d 'user=admin&password=SuperSecret123' http://127.0.0.1/
tcpdump -i any -n -A 'tcp port 443'
curl -k -d 'user=admin&password=SuperSecret123' https://127.0.0.1/
# --- System-wide crypto policy ---
update-crypto-policies --show
sudo update-crypto-policies --set FUTURE # then reboot / restart services
sudo update-crypto-policies --set DEFAULT
sudo update-crypto-policies --set DEFAULT:NO-SHA1
tail /var/log/httpd/ssl_error_log # when httpd refuses after FUTURE
openssl req -x509 -nodes -days 365 -newkey rsa:4096 \
-keyout /etc/pki/tls/private/localhost.key \
-out /etc/pki/tls/certs/localhost.crt \
-subj "/CN=$(hostname)"
# --- MariaDB hardening ---
ss -tulnp | grep 3306
# /etc/my.cnf.d/mariadb-server.cnf → bind-address=127.0.0.1
# optional: port=3307 then:
sudo ausearch -m avc -ts recent
sudo semanage port -a -t mysqld_port_t -p tcp 3307
systemctl restart mariadb
mariadb-secure-installation📺 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/terptelback • 9d ago
r/redhat • u/MajorCrafty6966 • 10d ago
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/a_shippus • 11d ago
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/AustinFastER • 11d ago
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 [email protected] address and the quarantine on our security appliance does not have them...
r/redhat • u/limaunion • 12d ago
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/Dismal_Lab_3954 • 13d ago
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/Rhopegorn • 13d ago
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/waldirio • 13d ago
Hello
Let's understand the difference between Update and Upgrade on Red Hat Satellite, also, implementing them in our hands on!
Enjoy it!
Wally