Skip to content

Commit

Permalink
man: Describe GPG key behavior
Browse files Browse the repository at this point in the history
Came up on chat, and this is important since it differs from
traditional `rpm/dnf` today.
  • Loading branch information
cgwalters committed Aug 25, 2023
1 parent 94b039a commit 6033e5a
Showing 1 changed file with 25 additions and 0 deletions.
25 changes: 25 additions & 0 deletions man/rpm-ostree.xml
Original file line number Diff line number Diff line change
Expand Up @@ -897,6 +897,31 @@ $ systemctl start postgresql # Some setup required

</refsect1>

<refsect1>
<title>Repository configuration and GPG keys</title>

<para>
rpm-ostree uses the libdnf shared library, which honors <literal>/etc/yum.repos.d</literal>.
Note that rpm-md (yum/dnf) repositories are only checked if client-side package layering is
enabled.
</para>

<para>
However, the behavior for GPG keys is slightly different from a traditional <command>rpm</command>
system. Essentially, all GPG keys in <literal>/etc/pki/rpm-gpg</literal> are loaded and trusted.
The <literal>.repo</literal> file should reference the file path in there.
</para>
<para>
The <literal>rpm --import /path/to/key.gpg</literal> command will not function today on a
live/booted system because rpm tries to write directly to the RPM database.
</para>

<para>
However, during a container build process, the RPM database is writable and such changes will
persist.
</para>
</refsect1>

<refsect1>
<title>See Also</title>

Expand Down

0 comments on commit 6033e5a

Please sign in to comment.