# rhel Red Hat Enterprise Linux (RHEL) is a flexible, stable operating system foundation for hybrid-cloud innovation and applications across physical, virtual, private-cloud, public-cloud, and edge deployments. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## auditd: audita el sistema en Linux DevFeed: [auditd: audita el sistema en Linux]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-01T11:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Linux](), [Kernel](), [Debian](), [rhel](), [Ubuntu]() Tags: [debian](), [kernel](), [linux](), [logs](), [rhel](), [ubuntu]() ### AI overview A Spanish tutorial on using auditd for Linux system auditing. It explains how auditd records file access and system calls with the user, process, and time; how to install and activate it across major Linux distributions; how to write file and syscall rules; how to use keys for searching events; and how to persist rules with augenrules. ### Source excerpt auditd registra en el kernel quién cambió qué archivo y cuándo. Aprende reglas -w y -a/-S, ausearch, aureport y el modo inmutable -e 2. ## Montar un servidor DNS autoritativo con BIND9 DevFeed: [Montar un servidor DNS autoritativo con BIND9]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-15T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Linux](), [Debian](), [rhel](), [Ubuntu]() Tags: [apparmor](), [debian](), [dns](), [linux](), [resolver](), [retry](), [rhel](), [soa](), [ttl](), [ubuntu]() ### AI overview A tutorial on setting up an authoritative BIND9 DNS server on Linux, covering forward and reverse zones, SOA values, common record types, distribution-specific paths, and distinctions from Pi-hole. ### Source excerpt BIND9 autoritativo en Linux: zonas directas e inversas, servidor secundario con TSIG, rndc y buenas prácticas de seguridad. ## Proxy inverso con Nginx: guía práctica DevFeed: [Proxy inverso con Nginx: guía práctica]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-01-09T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [nginx](), [proxy](), [rate-limiting](), [let's encrypt](), [rhel](), [SELinux]() Tags: [let-s-encrypt](), [nginx](), [proxy](), [rate-limiting](), [rhel](), [selinux](), [ssl]() ### AI overview A practical Spanish-language guide to using Nginx as a reverse proxy. It covers routing traffic to internal applications, HTTPS with Let's Encrypt, load balancing, upload and proxy timeout settings, request-rate limiting, gzip compression, security headers, and the 502 issue associated with SELinux on RHEL. ### Source excerpt Nginx como proxy inverso: subidas de archivos grandes, timeouts, rate limiting, gzip y el clásico 502 por SELinux en RHEL. ## How to Pin Versions in Yum or Dnf for RHEL or CentOS Linux DevFeed: [How to Pin Versions in Yum or Dnf for RHEL or CentOS Linux]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2024-05-07T09:01:47Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [dnf](), [Linux](), [centos](), [rhel](), [Fedora]() Tags: [centos](), [dnf](), [fedora](), [how-to](), [howto](), [linux](), [linux-distribution](), [pin](), [redhat-fedora-linux](), [rhel](), [sys-admin](), [tips]() ### AI overview A tutorial explains how to pin packages to specific versions on RHEL, CentOS, Fedora, and related distributions using yum or dnf. It covers installing the versionlock plugin, locking packages such as PHP and nginx, listing or removing locks, and checking blocked updates. ### Source excerpt CentOS, RHEL (Red Hat Enterprise Linux), Fedora and other clones of RHEL, such as Oracle, Alma, and Rocky, offer support for version pinning. This feature allows developers and system administrators to lock a particular package to a specific version, preventing it from being automatically updated by yum or dnf commands. Sometimes, it is necessary to protect packages from being updated to newer versions to avoid incompatibility issues with your applications. For example, you can lock down PHP version 8.3.6 and avoid using updated PHP version 8.4. Let us see how to lock a package to a specific version, only exclude a package from yum update or dnf update on a CentOS, RHEL, Fedora, and friends. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to Pin Versions in Yum or Dnf for RHEL or CentOS Linux appeared first on nixCraft. ## FIPS 140-2 experimental support DevFeed: [FIPS 140-2 experimental support]() Original publisher: [Read original article]() Author: Marek Posolda Published: 2022-11-16T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Cryptography](), [Security](), [openjdk](), [rhel]() Tags: [cryptography](), [fips](), [idm](), [isaac](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [openjdk](), [release](), [rhel](), [saml](), [security](), [sso]() ### AI overview Keycloak 20 introduces experimental support for FIPS 140-2. The article explains its reliance on Java cryptography providers and BouncyCastle, describes running Keycloak on a FIPS-compliant RHEL and Java environment, and notes limitations affecting SAML, Kerberos/SPNEGO, X.509 authentication, and password length in stricter mode. ### Source excerpt We are glad to announce that latest Keycloak 20 release contains experimental support for FIPS 140-2! The FIPS 140-2 standard is a set of requirements for cryptography modules, which needs to be met for the software used by U.S. governments and related parties. The FIPS compliant software should use only secure cryptography algorithms allowed by the FIPS specification and must use them in a secured way. Keycloak does not directly implement any cryptography algorithms, however it internally needs to use lots of cryptography functionalities. For this purpose, Keycloak mostly relies on the Java cryptography SPI and 3rd party libraries for implementing cryptography related functionality - especially the BouncyCastle library. FIPS support is usually enabled at the OS level. For example, during installation of RHEL 8.6 , you can enable kernel flag during OS installation to make sure that your OS is FIPS compliant. When FIPS is enabled at the OS level, it means that various packages including OpenJDK are also set to be FIPS compliant and are pre-configured to rely on FIPS approved functions. For example java.security configuration file is pre-configured to contain only FIPS compliant security providers. The FIPS support in Keycloak means that the Keycloak server can run on the FIPS compliant OS with FIPS compliant Java. It also means that the Keycloak server is FIPS compliant and can be used by parties, which strictly require FIPS 140-2 support. Even if you do not use the FIPS enabled OS, you can still try the FIPS enabled Keycloak server by using custom java.security file with only BouncyCastle-FIPS security providers configured as described in the instructions below in the step 4. Thanks to David Anderson, who contributed parts of this feature. Also, thanks to Sudeep Das and Isaac Jensen for their initial prototype effort, which was used as an inspiration. Instructions Instructions for how to try FIPS support in Keycloak are here. Conclusion We will be happy for you to t