No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
Install package from the repository to which the new GPG key belongs to. Crash an application from this package - abrt should ignore it this time. Leave gpg check on and import the gpg key from the repo (if you haven't already). Add the gpg key into ABRT config, crash something from the package - and this time it should be reported. | Install package from the repository to which the new GPG key belongs to. Crash an application from this package - abrt should ignore it this time. Leave gpg check on and import the gpg key from the repo (if you haven't already). Add the gpg key into ABRT config, crash something from the package - and this time it should be reported. | ||
'''<fixme: which repository to add as an example? how to install gpg key?>''' | '''<fixme: which repository to add as an example? how to install gpg key?>''' | ||
Revision as of 14:23, 18 August 2009
Description
This is testing ABRT GPG check using custom GPG Keys That means you can add other trusted GPG keys used to sign packages from some repository (e.g. RPM Fusion). See also QA:Testcase_abrt_GPG_check.
How to test
Edit config file /etc/abrt/abrt.conf, where you should find lines:
EnableOpenGPG = yes OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora, /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora
Set EnableOpenGPG to yes. Add path to GPG signature, delimited by colon.
Restart ABRT:
# service abrt restart
Install package from the repository to which the new GPG key belongs to. Crash an application from this package - abrt should ignore it this time. Leave gpg check on and import the gpg key from the repo (if you haven't already). Add the gpg key into ABRT config, crash something from the package - and this time it should be reported.
<fixme: which repository to add as an example? how to install gpg key?>
Expected Results
ABRT should notice only crashes of applications from signed packages when EnableOpenGPG=yes, it should ignore packages from unsupported archives