Robert Lopez:
> Wietse, No I did not! Now I have. Thanks.
>
> Is this sufficient to know all is ok:
>
> # gpg --verify postfix-2.10.0.tar.gz.sig postfix-2.10.0.tar.gz
> gpg: Signature made Mon 11 Feb 2013 09:19:00 AM MST using RSA key ID
> C12BCD99
> gpg: Good signature from "Wietse Venema "
> g
Wietse, No I did not! Now I have. Thanks.
Is this sufficient to know all is ok:
# gpg --verify postfix-2.10.0.tar.gz.sig postfix-2.10.0.tar.gz
gpg: Signature made Mon 11 Feb 2013 09:19:00 AM MST using RSA key ID
C12BCD99
gpg: Good signature from "Wietse Venema "
gpg: WARNING: This key is not cer
Robert Lopez:
> For myself, my gpg stuff works well for what I use it (Google Apps) but is
> apparently broken for importing new keys:
> $ gpg -v --import wietse.pgp
> gpg: can't open `wietse.pgp': No such file or directory
Do you have the `wietse.pgp' file? I have a copy linked from
the Postfix
Now that I know what it is, searching for "gpg postfix" I keep reading of
others who never got it to work (rsa or not discussion etc). I have yet to
find a posting of it working.
For myself, my gpg stuff works well for what I use it (Google Apps) but is
apparently broken for importing new keys:
$
On Mon, Apr 01, 2013 at 02:11:53PM -0600, Robert Lopez wrote:
> How do I get the md5sum for postfix-2.10.0.tar.gz out of the
> postfix-2.10.0.tar.gz.sig file?
The sig file is a GPG signature. Get the public key and verify the
signature:
gpg postfix-2.10.0.tar.gz.sig
(with postfix-2.10.0.tar.gz
