Skip to content

Commit fd64cfa

Browse files
Show importing a GPG pub key for all Client OS
The location of GPG public keys differ between EL, SLES, and Debian/Ubuntu. affects nightly to at least 3.12 Fixes a broken link on https://docs.orcharhino.com/or/docs/sources/guides/ubuntu/managing_content/importing_content.html#Extracting_GPG_Public_Key_Fingerprints_from_Release_Files_content-management
1 parent 0b238af commit fd64cfa

File tree

1 file changed

+17
-3
lines changed

1 file changed

+17
-3
lines changed

guides/common/modules/proc_importing-a-custom-gpg-key.adoc

Lines changed: 17 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ endif::[]
1010

1111
To use the CLI instead of the {ProjectWebUI}, see the xref:cli-importing-a-gpg-key[].
1212

13-
ifdef::client-content-dnf[]
1413
.Prerequisites
14+
ifdef::client-content-dnf[]
1515
Ensure that you have a copy of the GPG key used to sign the RPM content that you want to use and manage in {Project}.
1616
Most RPM distribution providers provide their GPG Key on their website.
1717
You can also extract this manually from an RPM:
@@ -31,9 +31,14 @@ $ rpm2cpio _example-9.5-2.noarch.rpm_ | cpio -idmv
3131

3232
The GPG key is located relative to the extraction at `etc/pki/rpm-gpg/RPM-GPG-KEY-_EXAMPLE-95_`.
3333
endif::[]
34+
ifndef::client-content-dnf[]
35+
* Extract the GPG public key fingerprints from a signed `Release` file for Deb content.
36+
For more information, see xref:Extracting_GPG_Public_Key_Fingerprints_from_Release_Files_{context}[].
37+
endif::[]
3438

3539
.Procedure
36-
. In the {ProjectWebUI}, navigate to *Content* > *Content Credentials* and in the upper-right of the window, click *Create Content Credential*.
40+
. In the {ProjectWebUI}, navigate to *Content* > *Content Credentials*.
41+
. Click *Create Content Credential*.
3742
. Enter the name of your repository and select *GPG Key* from the *Type* list.
3843
. Either paste the GPG key into the *Content Credential Contents* field, or click *Browse* and select the GPG key file that you want to import.
3944
+
@@ -60,12 +65,16 @@ Wl5GnzcLGAnUSRamfqGUWcyMMinHHIKIc1X1P4I=
6065

6166
[id="cli-importing-a-gpg-key"]
6267
.CLI procedure
63-
6468
. Copy the GPG key to your {ProjectServer}:
6569
+
6670
[options="nowrap" subs="+quotes,attributes"]
6771
----
72+
ifdef::client-content-dnf[]
6873
$ scp ~/etc/pki/rpm-gpg/RPM-GPG-KEY-_EXAMPLE-95_ root@{foreman-example-com}:~/.
74+
endif::[]
75+
ifndef::client-content-dnf[]
76+
$ scp ~/_My_GPG_Public_Key_ root@{foreman-example-com}:~/.
77+
endif::[]
6978
----
7079
. Upload the GPG key to {Project}:
7180
+
@@ -75,5 +84,10 @@ $ hammer content-credentials create \
7584
--content-type gpg_key \
7685
--name "_My_GPG_Key_" \
7786
--organization "_My_Organization_" \
87+
ifdef::client-content-dnf[]
7888
--path ~/RPM-GPG-KEY-_EXAMPLE-95_
89+
endif::[]
90+
ifndef::client-content-dnf[]
91+
--path ~/_My_GPG_Public_Key_
92+
endif::[]
7993
----

0 commit comments

Comments
 (0)