docs: explain "digest" vs "signature" fields for RPMs
This commit is contained in:
parent
c56c73a2e9
commit
5196f73d51
1 changed files with 2 additions and 1 deletions
|
|
@ -38,7 +38,8 @@ the public GPG key into their RPMDB::
|
|||
Payload SHA256 digest: OK
|
||||
MD5 digest: OK
|
||||
|
||||
Note there is no "RSA/SHA256 Signature" header field on the RPM here.
|
||||
Note there are only "digest" fields here, no "Signature" fields since this RPM
|
||||
is unsigned.
|
||||
|
||||
*Example: A GPG signature that rpmdb DOES trust*::
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue