Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
Apparently the SSL certificate used by the up2date program is expiring Real Soon Now. No matter what release you are using. If you do not get the new certificate, or update to an up2date that has the certificate, you will not be able to run up2date. Here is the email I got from them: ---------- Forwarded Message ---------- Subject: [RHSA-2003:267-01] New up2date available with updated SSL certificate authority file Date: Fri, 29 Aug 2003 07:39 -0400 From: bugzilla at redhat.com To: redhat-watch-list at redhat.com, bugtraq at securityfocus.com, full-disclosure at lists.netsys.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --------------------------------------------------------------------- Red Hat Security Advisory Synopsis: New up2date available with updated SSL certificate authority file Advisory ID: RHSA-2003:267-01 Issue date: 2003-08-29 Updated on: 2003-08-29 Product: Red Hat Linux Keywords: up2date Red Hat Network rhn_register Cross references: Obsoletes: - --------------------------------------------------------------------- 1. Topic: 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 Red Hat Linux 7.2 - i386, ia64 Red Hat Linux 7.3 - i386 Red Hat Linux 8.0 - i386 Red Hat Linux 9 - 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. 4. Solution: 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 https://rhn.redhat.com/help/latest-up2date.pxt For users who would prefer to install the new certificate directly, it is available at: https://rhn.redhat.com/help/ssl_cert.pxt 5. RPMs required: Red Hat Linux 7.1: SRPMS: ftp://updates.redhat.com/7.1/en/os/SRPMS/up2date-2.8.40-1.7.1.src.rpm i386: ftp://updates.redhat.com/7.1/en/os/i386/up2date-2.8.40-1.7.1.i386.rpm ftp://updates.redhat.com/7.1/en/os/i386/up2date-gnome-2.8.40-1.7.1.i386.rpm Red Hat Linux 7.2: SRPMS: ftp://updates.redhat.com/7.2/en/os/SRPMS/up2date-2.8.40-2.7.2.src.rpm i386: ftp://updates.redhat.com/7.2/en/os/i386/up2date-2.8.40-2.7.2.i386.rpm ftp://updates.redhat.com/7.2/en/os/i386/up2date-gnome-2.8.40-2.7.2.i386.rpm ia64: ftp://updates.redhat.com/7.2/en/os/ia64/up2date-2.8.40-2.7.2.ia64.rpm ftp://updates.redhat.com/7.2/en/os/ia64/up2date-gnome-2.8.40-2.7.2.ia64.rpm Red Hat Linux 7.3: SRPMS: ftp://updates.redhat.com/7.3/en/os/SRPMS/up2date-2.8.40-3.7.3.src.rpm i386: ftp://updates.redhat.com/7.3/en/os/i386/up2date-2.8.40-3.7.3.i386.rpm ftp://updates.redhat.com/7.3/en/os/i386/up2date-gnome-2.8.40-3.7.3.i386.rpm Red Hat Linux 8.0: SRPMS: ftp://updates.redhat.com/8.0/en/os/SRPMS/up2date-3.0.7.2-1.src.rpm i386: ftp://updates.redhat.com/8.0/en/os/i386/up2date-3.0.7.2-1.i386.rpm ftp://updates.redhat.com/8.0/en/os/i386/up2date-gnome-3.0.7.2-1.i386.rpm Red Hat Linux 9: SRPMS: ftp://updates.redhat.com/9/en/os/SRPMS/up2date-3.1.23.2-1.src.rpm i386: ftp://updates.redhat.com/9/en/os/i386/up2date-3.1.23.2-1.i386.rpm ftp://updates.redhat.com/9/en/os/i386/up2date-gnome-3.1.23.2-1.i386.rpm 6. Verification: MD5 sum Package Name - -------------------------------------------------------------------------- b67ea5065c3115d523e17561aac5cb7c 7.1/en/os/SRPMS/up2date-2.8.40-1.7.1.src.rpm 71f2f6e4bfcdee8f4f46ef037c7a1c8d 7.1/en/os/i386/up2date-2.8.40-1.7.1.i386.rpm 2205d1e5832dbb67d60103104eb59fec 7.1/en/os/i386/up2date-gnome-2.8.40-1.7.1.i386.rpm 3deea256b106e71ee6d5890639d872b3 7.2/en/os/SRPMS/up2date-2.8.40-2.7.2.src.rpm 21bc8e1f03e9f28590d46df60a9458b5 7.2/en/os/i386/up2date-2.8.40-2.7.2.i386.rpm 3d3d7c6dca73d521a0f541b859f13eb3 7.2/en/os/i386/up2date-gnome-2.8.40-2.7.2.i386.rpm ac5161a5bbe122896eccbc312bef9273 7.2/en/os/ia64/up2date-2.8.40-2.7.2.ia64.rpm c789fbf88d7faf82504eb4189b767f90 7.2/en/os/ia64/up2date-gnome-2.8.40-2.7.2.ia64.rpm 23d8868920cb7df21925669f04fb2ad2 7.3/en/os/SRPMS/up2date-2.8.40-3.7.3.src.rpm 3643d7774d7e60a1aeb79c8fecbf624c 7.3/en/os/i386/up2date-2.8.40-3.7.3.i386.rpm 89977334ec0d3a2a720c3303602fc8dd 7.3/en/os/i386/up2date-gnome-2.8.40-3.7.3.i386.rpm 17ad92db4579d046d84c84a16784ba98 8.0/en/os/SRPMS/up2date-3.0.7.2-1.src.rpm 15bc5dc918916bca3a5c29148979716e 8.0/en/os/i386/up2date-3.0.7.2-1.i386.rpm 1ae89cf79880f3bc5de7b86eb1d47a2b 8.0/en/os/i386/up2date-gnome-3.0.7.2-1.i386.rpm b8a5b2d548869a846cbaf373f3637555 9/en/os/SRPMS/up2date-3.1.23.2-1.src.rpm 3faabcb9cc610627fe378b88d0b2b928 9/en/os/i386/up2date-3.1.23.2-1.i386.rpm 733d0aca17c15af0b1fa709ba86337dc 9/en/os/i386/up2date-gnome-3.1.23.2-1.i386.rpm 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: md5sum <filename> 7. Contact: The Red Hat security contact is <secalert at redhat.com>. More contact details at https://www.redhat.com/solutions/security/news/contact.html Copyright 2003 Red Hat, Inc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/Tzt/XlSAg2UNWIIRAoUSAKCfwH7rc+4n4qDoAwqpeHOfvHHu7gCgmkhY qGnZb7YTmLpjhBxLWdWQLXs= =w6lI -----END PGP SIGNATURE----- _______________________________________________ Redhat-watch-list mailing list To unsubscribe, visit: https://www.redhat.com/mailman/listinfo/redhat-watch-list ------------------------------------------------------- -- ---------------------------------------------------------------------------- DDDD David Kramer david at thekramers.net http://thekramers.net DK KD DKK D You can't outrun Death forever. DK KD DDDD But you can make the bastard work for it.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |