| 1 |
|
| 2 |
All Bacula packages released on Source Forge after 8 June 2003 |
| 3 |
will be signed with the Bacula Distribution Verification Key. By |
| 4 |
obtaining a copy of the Bacula Distribution Verification Public |
| 5 |
key from either the home site (www.bacula.org) or from the Source |
| 6 |
Forge project page, (www.sourceforge.net/projects/bacula). you |
| 7 |
can verify that the code you have is complete, unaltered, and |
| 8 |
packaged by myself (Kern Sibbald) or D. Scott Barninger. |
| 9 |
|
| 10 |
Putting the Bacula Key in your Keyring: |
| 11 |
|
| 12 |
Once you download the Bacula public key, you must insert it in |
| 13 |
your keyring. The procedure will differ depending on whether you |
| 14 |
are using PGP or GPG. For GPG, assuming you have put the key |
| 15 |
in bacula.key, the procedure is: |
| 16 |
|
| 17 |
gpg --import bacula.key |
| 18 |
|
| 19 |
Verifying an RPM: |
| 20 |
|
| 21 |
The procedure for verification differs slightly if you are using |
| 22 |
rpms or tar.gz files. For rpms, the signature becomes part of the |
| 23 |
rpm package, and once the Bacula public key is in your keyring |
| 24 |
you check the package with: |
| 25 |
|
| 26 |
rpm --checksig bacula-1.xx.rpm |
| 27 |
|
| 28 |
Verifying tar files: |
| 29 |
|
| 30 |
Tar files are distributed as they always have been in the past, |
| 31 |
unchanged. However, for each xxxx.tar.gz file that is released there |
| 32 |
will be a second file released with the same name but with .sig |
| 33 |
appended, for example xxxx.tar.gz.sig. To verify the Bacula distribution, |
| 34 |
you download both the files and put them in the same directory, then |
| 35 |
for GPG, you use the following command to do the verification: |
| 36 |
|
| 37 |
gpg --verify xxxx.tar.gz.sig |
| 38 |
|