The public gpg key for rpm package signature verification
This package contains the gpg key that is used to sign official SuSE
rpm packages. It will be installed as a keyring in
/usr/lib/rpm/gnupg/pubring.gpg. Administrators who wish to add their
own keys to verify against should use the following commandline command
to add the key to the keyring as used by RPM:
gpg --no-options --no-default-keyring \ --keyring
/usr/lib/rpm/gnupg/pubring.gpg --import
- Developed at Base:System
- Sources inherited from project openSUSE:Factory
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:PowerPC/suse-build-key && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| build-container-d4ade9c3-5a2e9669.asc | 0000001000 1000 Bytes | |
| dumpsigs | 0000001944 1.9 KB | |
| gpg-pubkey-307e3d54-5aaa90a5.asc | 0000000615 615 Bytes | |
| gpg-pubkey-39db7c82-5f68629b.asc | 0000000972 972 Bytes | |
| gpg-pubkey-50a3dd1c-50f35137.asc | 0000001065 1.04 KB | |
| security_at_suse_de.asc | 0000009004 8.79 KB | |
| suse-build-key.changes | 0000010557 10.3 KB | |
| suse-build-key.spec | 0000003893 3.8 KB | |
| suse_ptf_key.asc | 0000001350 1.32 KB |
Revision 38 (latest revision is 43)
Dominique Leuenberger (dimstar_suse)
accepted
request 899890
from
Marcus Meissner (msmeissn)
(revision 38)
This syncs from SUSE:SLE-15:Update. the slightly non-incremental changelog can't be avoided. - suse build key extended (bsc#1176759) gpg-pubkey-39db7c82-5847eb1f.asc -> gpg-pubkey-39db7c82-5f68629b.asc - actually the container key is different from the build signing key. (PM-1845 bsc#1170347) - add a /usr/share/container-keys/ directory for GPG based Container verification. - Add the SUSE build key as "suse-container-key.asc". (PM-1845 bsc#1170347) - created a new security@suse.de communication key (bsc#1166334) - include ptf key in the key directory to avoid it being stripped via %doc stripping. (bsc#1044232) (forwarded request 899537 from dirkmueller)
Comments 0