Skip to content

Underline where to find info about storing GPG key permanently. #3861

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Underline where to find info about storing GPG key permanently. #3861

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion modules/administration/pages/custom-channels.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,9 @@ For example, execute the [command]``spacewalk-repo-sync`` from the command line
/usr/bin/spacewalk-repo-sync -c <channellabelname> -t yum
----

This command and procedure is for temporary GPG key synchronization only.
For storing the key permantenly, see this section later on.

The underlying [command]``zypper`` call will import the key, if it is available.
The {webui} does not offer this feature.

Expand Down Expand Up @@ -90,12 +93,16 @@ The key would also persist if the chroot environment would be cleaned.

.Procedure: Creating a Software Repository with GPG Key

. The command to import a key into the keyring is:
. On the container horst, the command to import a key into the keyring, is:

+

[source,shell]
----
mgradm gpg add /path/to/gpg.key
----

. For more information, see xref:client-configuration:autoinst-owngpgkey.adoc[].

[NOTE]
====
Expand Down
Loading