A number of packages in rhn-tools channel for rhel5 x86_64 are signed using the wrong key.

Solution Unverified - Updated -

Issue

  • A number of packages which are part of the rhn-tools channel for rhel5 x86_64 aren't signed using any of the keys
    listed on the keys page:

    https://access.redhat.com/site/security/team/key/#package

    An example package is auto-kickstart-ks-rhel-i386-ws-4-u6 which is signed using the wrong key 219180cddb42a60e.
    How to obtain a copy of the public key?

Environment

  • Red Hat Enterprise Linux 5
  • RHN Satellite 5.5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content