Red Hat Leftovers
-
Red Hat Announces Intent to Reach Net-Zero Operational Greenhouse Gas Emissions by 2030 [Ed: Shallow and meaningless greenwashing, citing some very distant future date]
Red Hat, the world's leading provider of open source solutions, today announced its ambition to achieve net-zero operational greenhouse gas (GHG) emissions by 2030 to address the global climate crisis.
Red Hat’s 2030 operational net-zero goal follows a science-aligned pathway to limit global warming to 1.5-degree Celsius above pre-industrial levels, and includes scope 1 and 2 emissions, and scope 3 emissions associated with Red Hat’s electricity consumption in third-party colocation data centers. The company has been through a rigorous exercise to develop an emissions accounting profile which establishes a baseline year of 2019.
-
Clevis performance improvements
This blog post showcases the performance improvements achieved in the process of booting unlock for Clevis LUKS-bound devices. By removing a single function from the boot process, boot time was shortened by 20% to 47%, depending on the scenario.
Clevis is a software framework that allows booting encrypted LUKS devices without manual intervention. This tool is part of Network-Bound Disk Encryption (NBDE). Clevis is the “client” side, although it is not strictly necessary to work against a server, and can be configured to read keys in different ways.
-
Red Hat Satellite 6.12.1 has been released
We are pleased to announce that Red Hat Satellite 6.12.1 is generally available as of January 18, 2023.
Red Hat Satellite is part of the Red Hat Smart Management subscription that makes it easier for enterprises to manage patching, provisioning, and subscription management of Red Hat Enterprise Linux infrastructure.
-
Taking patch management to the next level with automation
The term “patching” dates back to the days of punch cards when a programmer would literally patch a hole in a punch card to correct a bug. This allowed the programmer to correct mistakes without re-punching the entire card. What a painfully manual process that would have been to scale!
We have come a long way since the mid-twentieth century when this technique was used, but patching is as prevalent—if not significantly more so—today as ever as the threat landscape is evolving more rapidly and software release cycles shorten.