Rocky Linux 9.5 has been released. See our release announcement for more details.
Thank you for supporting Rocky Linux!
Sincerely,
Release Engineering @ The Rocky Linux Project
https://rockylinux.org
6 Likes
Great, but “release notes” links to an empty page. Is it supposed to send us to the upstream notes?
FWIW the link works fine for me. Goes to a page which contains the release notes.
Yes, the link works now. It appears none of the bugs or changes effect my use case, samba and backup server to home network. I’ll be installing when I can sit in front of the server as I don’t use automatic installs or packagekit when a kernel is involved.
1 Like
Great news.
I think the rocky9.5 entry is missing in libosinfo/osinfo-db though:
rocky8 | Rocky Linux 8 | 8 | http://rockylinux.org/rocky/8
rocky8-unknown | Rocky Linux 8 Unknown | 8-unknown | http://rockylinux.org/rocky/8-unknown
rocky8.4 | Rocky Linux 8.4 | 8.4 | http://rockylinux.org/rocky/8.4
rocky8.5 | Rocky Linux 8.5 | 8.5 | http://rockylinux.org/rocky/8.5
rocky8.6 | Rocky Linux 8.6 | 8.6 | http://rockylinux.org/rocky/8.6
rocky9 | Rocky Linux 9 | 9 | http://rockylinux.org/rocky/9
rocky9-unknown | Rocky Linux 9 Unknown | 9-unknown | http://rockylinux.org/rocky/9-unknown
rocky9.0 | Rocky Linux 9.0 | 9.0 | http://rockylinux.org/rocky/9.0
Hi
Is it possible to still upgrade to 9.4 from version 9.1 as my software does not work on 9.5. Wondering if there is an upgrade path to the version before the current or do i have no choice but to upgrade to the latest ?
This is intentional. See my reply here.
You can use the vault if you absolutely must use an older version. This will require modifying your repo files.
Note that this is not supported as 9.4 is end of life.
Using the vault will require you to modify your repo files. As stated before, using the vault is not supported by the project and the community.
Updating and running on the latest versions available is the only supported path for Rocky Linux.
Thank you for confirmig what I had suspected - much appreciated
Virtualbox box for Rocky 9.5 is missing.
The latest box version (4.0.0) links to an external image url, which doesn’t exist anymore because of the Rocky 9.4 move from Index of /pub/ to https://dl.rockylinux.org/vault/:
https://portal.cloud.hashicorp.com/vagrant/discover/rockylinux/9/versions/4.0.0
Does anybody know who is responsible for updating the virtual box boxes?
The way the Rocky box is using the above mentioned linking makes boxes unusable after each Rocky release. I think this should be fixed so you are able to use older Rocky version.
Success story, Mini PC, Intel N97
Blackview M80 acquired Dec 2024. Ran up Windows,
with Disk Manager shrunk C: now 800Gb free space.
Booted 9.5 Minimal on USB DVD. Installed fine.
Used reFind on a small USB stick to avoid bios hassles.
Leaving intact Windows on the internal disk.
Good news! but where is build log?
Hello,
One of our customers is using Rocky 9.5 image on his on-premises servers and now he is migrating its application into AWS public cloud.
The application will be running in Tel Aviv region (il-central-1) In your website the is no such region, How can our customer keep on using your OS?
Hi Rocky Linux Teams,
I have deploy several Rocky Link 9 servers in my site. All of them are upgraded to latest version, 9.5. The security team in my site used a nessux scanner to scan my Rocky Linux servers and found there were a critical CVE-2024-5535, I have to upgrade the openssl version from 3.2.2 to 3.2.3. when I use “sudo dnf update -y” it says that is the latest update and nothing to do. May I know how will openssl version 3.2.3 release in Rocky Linux 9.5? Thank you
According to one my release engineers, the images are already available in that region, just not listed on our website which will hopefully be addressed.
Openssl will not be rebased to any newer versions unless upstream plans on doing so. With that said, you can check rpm -q openssl --changelog | less and look for that CVE to see if it’s addressed. In majority of cases, backports are done to address security vulnerabilities. See below.
[nazu@router tmp]$ rpm -q openssl --changelog | grep CVE-2024-5535 -B1
* Wed Aug 21 2024 Clemens Lang <cllang@redhat.com> - 1:3.2.2-4
- Fix CVE-2024-5535: SSL_select_next_proto buffer overread
As shown above, that CVE was addressed back in August, which means an upgrade to 3.2.3 is not required nor necessary. Please read the red hat backports page for more information.
I would also suggest that you notify your security team to A) fix their scanner and B) send them the backports link on how backports are addressed in RHEL and RHEL derivatives.
This thread is for the announcement of a release and not for technical support. Please open a new thread in the help & support category if you have questions or need assistance from the community.
This thread is now closed.