|
|

楼主 |
发表于 2006-1-18 21:57:24
|
显示全部楼层
找到这样一段话,还是不太明白。一楼的sign是公匙吗?
Using GnuPG, verifying a signature should look like this:
% gpg --verify linux-2.3.9.tar.gz.sign linux-2.3.9.tar.gz
gpg: Signature made Mon Oct 9 23:48:38 2000 PDT using DSA key ID 517D0F0E
gpg: Good signature from "Linux Kernel Archives Verification Key <ftpadmin@kernel.org>"
Unless you have taken explicit steps to build a trust path to the Linux Kernel Archives Verification Key, you should expect to see a warning message akin to:
Could not find a valid trust path to the key. Let's see whether we
can assign some missing owner trust values.
No path leading to one of our keys found.
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
after gpg has verified the signature. You should not be alarmed by this warning.
Before you can do this, you must gpg --import the key below. This key is also available from most common PGP key servers, such as hkp://wwwkeys.pgp.net/0x517d0f0e ( http://wwwkeys.pgp.net:11371/pks ... ;search=0x517D0F0E). To import it from the keyserver using GnuPG, do:
gpg --keyserver wwwkeys.pgp.net --recv-keys 0x517D0F0E
The previously used PGP 2.6 key has been revoked; see below for the revokation certificate. |
|