(ABRT_GPG_Keys) |
(see also QA:Testcase_abrt_GPG_check) |
||
| Line 2: | Line 2: | ||
|description= | |description= | ||
This is testing [[Features/ABRT|ABRT]] GPG check using '''custom GPG Keys''' | This is testing [[Features/ABRT|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) | 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]]. | ||
|actions= | |actions= | ||
Revision as of 18:58, 17 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
Set gpg EnableOpenGPG to yes. Instal some package from fusion rpm (or any other repo). 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: how to add key to config? Comma delimited? Please provide example...>
Expected Results
ABRT should notice only crashes of applications from signed packages when EnableOpenGPG=yes, it should ignore packages from unsupported archives