Red Hat Linux Advisory: up2dateAug 29, 2003, 16:59 (11 Talkback[s])
Red Hat Security Advisory
New versions of the up2date and rhn_register clients are available and are required for continued access to Red Hat Network.
2. Relevant releases/architectures:
Red Hat Linux 7.1 - i386
3. Problem description:
The rhn_register and up2date packages contain the software necessary to take advantage of Red Hat Network functionality.
This erratum includes an updated RHNS-CA-CERT file, which contains a new CA certificate. This new certificate is needed so that up2date can continue to communicate with Red Hat Network after 28 August 2003. Without this updated certificate, users will see SSL Connection Errors reported by up2date or rhn_register.
All users must upgrade to these erratum packages in order to continue to use Red Hat Network. This includes both interactive use of up2date, as well as actions scheduled by the RHN website.
Before applying this update, make sure all previously released errata relevant to your system have been applied.
To update all RPMs for your particular architecture, run:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory only contains the desired RPMs.
Because the previous Certificate Authority has expired, up2date will present 'SSL Certificate Errors' if you attempt to use it to apply this errata. Therefore, this update cannot be applied directly with up2date and instead must be applied as indicated above.
In addition to the Red Hat FTP site, the latest versions of up2date and rhn_register are also available at
For users who would prefer to install the new certificate directly, it is available at:
5. RPMs required:
Red Hat Linux 7.1:
Red Hat Linux 7.2:
Red Hat Linux 7.3:
Red Hat Linux 8.0:
Red Hat Linux 9:
MD5 sum Package Name
These packages are GPG signed by Red Hat for security. Our key is available from https://www.redhat.com/security/keys.html
You can verify each package with the following command:
rpm --checksig -v <filename>
If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command:
The Red Hat security contact is <firstname.lastname@example.org>. More contact details at https://www.redhat.com/solutions/security/news/contact.html
Copyright 2003 Red Hat, Inc.
0 Talkback[s] (click to add your comment)