RE: up2date invalid cert
Bingner Sam J Contractor PACAF CSS/SCHE <[email protected]>
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <[email protected]> |
my guess is that you need to re-run rhn_register so you can get a client cert signed by the current server.... or your client cert is still right and up2date has been changed to point back to RedHat's servers instead of the current server. Sam -----Original Message----- From: Brian DeFeyter [mailto:[email protected]] Sent: Wednesday, April 03, 2002 8:39 AM To: [email protected] Subject: [Current-server] up2date invalid cert I would think this was answered already somewhere, but I didn't see it in the archives. After running a pretty much stock to current 7.2 updates with current (about 70 RPMS upgraded) I'm getting errors with the up2date tool. I first noticed that it upgraded up2date, and that the RHNS-CA-CERT was replaced with the redhat version. I copied that back over, but I'm getting this error: /usr/sbin/up2date -l Error communicating with server. The message was: Invalid client certificate Any ideas on what might be happening? I know for sure that the client cert is now the cert I generated locally.. and am using elsewhere. I can provide dumps of server output if that would be helpful too. Thanks, - Brian