r/redhat • • Sep 19 '26

Move cert discussions to r/redhat_certification

91 Upvotes

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 • • 1d ago

The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9 | Red Hat Developer

Thumbnail
developers.redhat.com
27 Upvotes

When a critical outage hits a production environment, time is your most crucial resource. Systems going down, unresponsive microservices, kernel panics, or sudden I/O bottlenecks can quickly jeopardize core business operations. For systems administrators, site reliability engineers (SRE), and DevOps teams managing enterprise workloads on Red Hat Enterprise Linux 8 or 9 (RHEL), having a disciplined and reproducible standard operating procedure (SOP) is what separates a blink from a catastrophe.

TL;DR
RHEL 8 and 9 critical outage triage uses severity levels 1–4 with Red Hat Support SLAs. Systematic checks cover identity, CPU, memory, storage, I/O, systemd, network, logs, and SELinux to isolate constraints and preserve evidence.


r/redhat • • 2d ago

4 YOE in IT Support + recently got my RHCSA, struggling to land Linux Admin interviews. Where do I go from here?

15 Upvotes

Hey everyone, looking for some honest advice on my career pivot.

I’ve been working in IT Support for the past 4 years and recently decided to make the jump into Linux Administration and related infrastructure roles. To prove my skills on paper and get past HR filters, I studied for and passed my RHCSA.

I was hoping that combining 4 years of general IT/support experience with a hands-on cert like the RHCSA would at least start getting me shortlisted for Junior/Mid-level Linux Admin roles. Instead, I’m hitting a wall:

  • I’m barely getting any callbacks or interview invites.
  • Pure "Linux Admin" roles seem scarce or strictly ask for 3+ years of dedicated production Linux experience (which I don't have in my official title).
  • Most roles I see want Linux bundled with Cloud (AWS/Azure), Ansible, Docker/Kubernetes, or heavy scripting.

I feel like I’m stuck in that awkward middle ground—overqualified for basic L1 helpdesk, yet underqualified on paper for pure SysAdmin roles because my last 4 years were in Support.

For those of you who successfully made the jump from Support to Linux Admin/Infra/Cloud:

  1. What should my next immediate step be? Should I start learning Ansible/RHCE, AWS, or Docker/K8s to make my profile more attractive, or focus on building a homelab portfolio?
  2. What job titles should I actually be targeting? Are there specific stepping-stone roles (like NOC, Application Support, Linux Support Engineer, Junior DevOps) that bridge this gap better than searching strictly for "Linux Administrator"?
  3. Resume tips: How do I frame 4 years of Support experience so recruiters actually value it rather than dismissing it as "just helpdesk"?

Any reality checks or roadmap suggestions would be hugely appreciated. Thanks!


r/redhat • • 1d ago

ruby version for satellite 6.20

2 Upvotes

Is anyone running the Early Access to satellite 6.20?

Can someone post the Ruby version is that's being bundled with it?


r/redhat • • 2d ago

nginx2root: fixed nginx packages for RHEL 9 (base 1.20 + AppStream 1.22, 1.24, 1.26)

17 Upvotes

Disclosure: I work at Hosted Power, a hosting company. This is free and open source.

Red Hat still lists RHEL 9 nginx (default 1.20 and the 1.22, 1.24 and 1.26 streams) as affected by nginx2root (CVE-2026-123007 and four related CVEs). If you have a subscription, Red Hat support is your first stop. This is for boxes you can't leave exposed in the meantime.

We built the fixes into RHEL's own nginx packages: base 1.20 and AppStream 1.22, 1.24 and 1.26. Same package names, modularity label, config and modules; the installer rejects the wrong vendor or stream. Versions sit just below the next Red Hat update, so a normal dnf update moves you to Red Hat's package when it ships.

https://github.com/HOSTED-POWER/nginx2root-patches

Switching HTTP/2 off only blocks 2 of the 12 vulnerabilities these packages fix, so it isn't a fix on its own.

Update: RHEL 8 (nginx:1.24) and RHEL 10 are covered now too (v1.6.1, v1.7.0). Correction: RHEL 10 does not have Red Hat's fix yet; it still ships 1.26.3-16.el10_3.1 from before nginx2root.


r/redhat • • 3d ago

Grub issue when upgrading rhel 9 to 10 using Leapp

10 Upvotes

Hi all,

I am somewhat new to rhel, I wanted to upgrade my current rhel 9.8 to rhel 10.2 version.

I found this can be done with Leapp tool. I manage to remove all inhibitor errors. And performed the upgrade, now my VM isn't coming up.

Its a VM running on Bare metal server using libvirt. I am not able to access console, nor getting any kind of logs.

I suspect it's due to Grub upgrade, it was mentioned in preupgrade with no actionables.

I wanted to know, did anybody has done such kind of activity or someone faced similar kind of issue, would be a great help if I can get any direction.

-----------

Risk Factor: high

Title: GRUB2 core will be automatically updated during the upgrade

Summary: On legacy (BIOS) systems, GRUB2 core (located in the gap between the MBR and the first partition) cannot be updated during the remaining transaction and Leapp has to initiate the update running "grub2-install" after the transaction. No action needed before the upgrade. After the upgrade, it is recommended to check the GRUB configuration.

----------


r/redhat • • 4d ago

Follow-up: I built the "Linux time travel" tool I asked about here. Looking for people to try it

17 Upvotes

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 dst10.0.4.21and 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 (4-day soak) │ Busy server (benchmark) │
  ├───────────┼─────────────────────┼─────────────────────────┼─────────────────────────┤
  │ 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 kept │ ~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 • • 4d ago

OCP/RH-Operators on OKD

Thumbnail
reddit.com
2 Upvotes

r/redhat • • 4d ago

Introducing Cerbere AG: Runtime security and observability for AI agents

2 Upvotes

r/redhat • • 4d ago

RHEL compatibility questions for a stdlib-only health checker

10 Upvotes

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 • • 4d ago

GAMING ON RHEL

0 Upvotes

So yeah, i will use RHEL for DD(daily drive), is gaming something possible on it?


r/redhat • • 6d ago

Who Else Has Earned the Red Hat? What Year Did You Get Certified?

Thumbnail reddit.com
0 Upvotes

r/redhat • • 7d ago

Epel in environment

26 Upvotes

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 • • 8d ago

You're in: Satellite 6.20 limited availability access inside

9 Upvotes

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 • • 9d ago

Absolute minimal LDAP setup for software install

17 Upvotes

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 • • 10d ago

Does Red Hat care if employees are working from a remote location?

10 Upvotes

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 • • 10d ago

Red Hat Offline Knowledge Portal: Complete Installation & Setup

Thumbnail
youtu.be
38 Upvotes

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 • • 11d ago

Open Source Security Signals | Q3 2026

Thumbnail
redhat.com
0 Upvotes

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 • • 12d ago

Harden What You Can't Turn Off — mount options, TLS, crypto policies, and MariaDB locking-down from Into the Terminal Ep. 205

25 Upvotes

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:

  1. Contain disk-full disasters — if /var fills up, logging and services get unhappy, but you can still log in and read /etc
  2. 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 optionWhat it does
nosuidIgnores setuid and setgid bits — planted root-setuid binaries can't escalate
noexecNothing on this filesystem can be executed (even if the execute bit is set)
nodevDevice 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 stuck

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/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.)


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.

CommandWhat 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.

CommandWhat it does
update-crypto-policies --showPrint the active policy (usually DEFAULT out of the box)
update-crypto-policies --set FUTURERaise the floor — refuse weaker algorithms/key sizes
update-crypto-policies --set DEFAULTBack to the sane modern baseline
update-crypto-policies --set LEGACYLoosen for ancient gear (going the wrong way — last resort)
update-crypto-policies --set DEFAULT:NO-SHA1Surgical 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)
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 FUTURE

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

ss -tulnp | grep 3306

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
systemctl 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.)

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.

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 mariadb

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:

StepWhy it matters
Switch root to UNIX socket authRoot DB access tied to the local Linux account / socket — not a network password
Set a root passwordOut-of-box often has none
Remove anonymous usersDefault anonymous accounts are free attack surface
Disallow remote root loginDefense in depth even after socket auth
Remove the test databaseOptional in labs / handoff environments; usually gone before prod
Reload privilege tablesApply now, or defer to a maintenance window

5. More you can still do (discussed, not fully demoed)

Hardening ideaWhy
local-infile=0Disable LOAD DATA LOCAL INFILE — harder for a compromised client/session to slurp files off the server
Password validation pluginEnforce password quality at the DB layer
Scope your GRANTsGRANT 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


Quick Reference Card

# --- 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

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 • • 12d ago

Job opportunities after clearing rhcsa exam?

1 Upvotes

r/redhat • • 12d ago

Transitioning from hospitality to Linux

0 Upvotes

​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 • • 13d ago

Who is the person in the Kernel Development icon in old Red Hat Linux installers?

Post image
3 Upvotes

r/redhat • • 14d ago

Job opportunities

3 Upvotes

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 • • 15d ago

Redhat Advisories?

7 Upvotes

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...