From Fedora Project Wiki

mNo edit summary
(proof and make clearer. also, we can't refer directly to rpmfusion in the wiki)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=
|description=
This is testing [[Features/ABRT|ABRT]] GPG check using '''custom GPG Keys'''
This test case checks whether [[Features/ABRT|ABRT]] can GPG check using custom GPG keys. That means you can add trusted GPG keys used to sign packages from third-party repositories. See also [[QA:Testcase_abrt_GPG_check]].
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]].
{{admon/important|This test case can run only with correctly signed packages.|This test case can't be run on Rawhide or Rawhide-based builds because the packages are not properly signed in these distributions.}}
{{admon/important|This test case can't be tested on Rawhide or provided LiveCD because the packages are not properly signed in these distributions.}}
|actions=
|actions=
Edit config file /etc/abrt/abrt.conf, where you should find lines:
# Edit config file {{filename|/etc/abrt/abrt.conf}}, and make sure ''OpenGPGCheck'' is set to yes.
<pre>
# Install a package which is signed, but not with an official Fedora project signature - such as a package from a popular third-party repository - and cause an application from the package to crash.
OpenGPGCheck = yes
# Add the GPG key with which the package is signed to the file {{filename|/etc/abrt/gpg_keys}}. Every separate key should be on a new line.
</pre>
# Restart ABRT with the command {{command|su -c service abrtd restart}}.
 
# Again cause the application to crash.
Set ''OpenGPGCheck'' to ''yes''.
 
You can add/remove gpg keys in /etc/abrt/gpg_keys every key has to be on the new line.
Restart ABRT: <pre># service abrtd restart</pre>
 
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.
 
You can [http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-rawhide.noarch.rpm add] RPMFusion repository, install some package from this repository and kill the app from this
package.  
 
# ABRT should ignore by default
# If you want ABRT to not ignore this packages you need to:
## add /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-* keys (depends on which repo do you use) to /etc/abrt/gpg_keys
## restart abrtd
 
 
|results=
|results=
ABRT should notice only crashes of applications from signed packages when OpenGPGCheck = yes, it should ignore packages from unsupported archives
# The first crash should not be reported by ABRT.
# The second crash should be reported by ABRT.
}}
}}
[[Category:ABRT_Test_Cases]]
[[Category:ABRT_Test_Cases]]

Revision as of 21:59, 31 March 2010

Description

This test case checks whether ABRT can GPG check using custom GPG keys. That means you can add trusted GPG keys used to sign packages from third-party repositories. See also QA:Testcase_abrt_GPG_check.

Important.png
This test case can run only with correctly signed packages.
This test case can't be run on Rawhide or Rawhide-based builds because the packages are not properly signed in these distributions.


How to test

  1. Edit config file /etc/abrt/abrt.conf, and make sure OpenGPGCheck is set to yes.
  2. Install a package which is signed, but not with an official Fedora project signature - such as a package from a popular third-party repository - and cause an application from the package to crash.
  3. Add the GPG key with which the package is signed to the file /etc/abrt/gpg_keys. Every separate key should be on a new line.
  4. Restart ABRT with the command su -c service abrtd restart.
  5. Again cause the application to crash.

Expected Results

  1. The first crash should not be reported by ABRT.
  2. The second crash should be reported by ABRT.