Difference between revisions of "DPI908/SBR600 RPM Signing Lab"
Chris Tyler (talk | contribs) (Created page with 'Category:DPI908/SBR600 Labs = Purpose = To learn how to create a repository. = Background Resources = Signing and Creating a Repository for RPM Packages = Required Re…') |
Chris Tyler (talk | contribs) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | [[Category:DPI908/SBR600 Labs]] | + | [[Category:DPI908/SBR600 Labs]][[Category: SBR600 Labs]] |
= Purpose = | = Purpose = | ||
− | To learn how to | + | To learn how to sign RPM packages. |
= Background Resources = | = Background Resources = | ||
Line 15: | Line 15: | ||
= Preparation = | = Preparation = | ||
− | + | Install these packages if they are not already installed: | |
− | + | # rpm-sign | |
− | + | # gnupg | |
= Steps = | = Steps = |
Latest revision as of 15:17, 16 September 2013
Purpose
To learn how to sign RPM packages.
Background Resources
Signing and Creating a Repository for RPM Packages
Required Resources
Before starting this lab, you will need:
- The RPMs from the previous lab.
Preparation
Install these packages if they are not already installed:
- rpm-sign
- gnupg
Steps
Using the procedures on the Signing and Creating a Repository for RPM Packages page:
- Create gpg certificates
- Sign your RPM packages
- Create the ASCII public key file
Deliverable
Create a blog post describing your experience. Include:
- Notes on what you did, and what worked and didn't work.
- The results, including a link to one signed RPM package and your ASCII public key file.
- Your reflections on the tools, process, and experience.