On applique la m�me m�thode pour d�chiffrer un message et en v�rifier la signature:
gpg -d -v
bash-2.05b$ gpg -d -v gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information -----BEGIN PGP MESSAGE----- Version: GnuPG v1.2.3 (GNU/Linux) ... -----END PGP MESSAGE----- gpg: armor header: Version: GnuPG v1.2.3 (GNU/Linux) gpg: public key is 541A4468 gpg: using secondary key 541A4468 instead of primary key 920625BC You need a passphrase to unlock the secret key for user: "Julien Francoz (CoCoZ) <[email protected]>" gpg: using secondary key 541A4468 instead of primary key 920625BC 2048-bit ELG-E key, ID 541A4468, created 2003-11-07 (main key ID 920625BC) gpg: encrypted with 2048-bit ELG-E key, ID 541A4468, created 2003-11-07 "Julien Francoz (CoCoZ) <[email protected]>" gpg: AES encrypted data gpg: original file name='test' azerty gpg: Signature made Sat Dec 27 23:13:53 2003 CET using DSA key ID 2F3C1A23 gpg: Good signature from "Antoine (ToTo) <[email protected]>" gpg: binary signature, digest algorithm SHA1 bash-2.05b$ |
On voit donc que le message azerty a �t� correctement sign� et chiffr� par Toto, et correctement d�chiffr� et v�rifi� par CoCoZ.
| Pr�c�dent | Sommaire | Suivant |
| Signer et chiffrer un message | Niveau sup�rieur | Int�gration de GnuPG dans d'autres programmes |