Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • Import GPG Key for 3rd-party channel in Satellite

    Posted on

    We have added the EPEL channel to our Base Channels (which then gets cloned).

    I retrieved EPEL GPG keys and publish them in /pub/RPM-GPG-KEY-epel (/pub/RPM-GPG-KEY-epel-6) on my Satellite.

    [root@rhnsat01 2014-09-03]# spacecmd softwarechannel_details  cln14wk25-epel-x86_64-server-5  | sed 's/XXX.YYY/mycompany/g'
    INFO: Connected to https://localhost/rpc/api as satman
    Label:              cln14wk25-epel-x86_64-server-5
    Name:               cln14wk25-epel-x86_64-server-5
    Architecture:       x86_64
    Parent:             cln14wk25-rhel-x86_64-server-5
    Systems Subscribed: 49
    Number of Packages: 8683
    
    Summary
    -------
    cln14wk25-epel-x86_64-server-5
    
    GPG Key:            217521F6
    GPG Fingerprint:    B940 BE07 7D71 0A28 7D7F  2DD1 119C C036 2175 21F6
    GPG URL:            http://rhnsat01.mycompany.com/pub/RPM-GPG-KEY-epel
    

    I guess I had hoped that the key would be "auto-imported" when I had subscribed a host to that child-channel?

    How are other folks managing the GPG keys? It is easy enough to run: rpm --import http://rhnsat01.mycompany.com/pub/RPM-GPG-KEY-epel or disable gpgcheck.

    If someone has advice, or knows which doc I should be looking at, it would be appreciated.

    Thanks!

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat