I'm running FreeBSD 9.0 and I've installed both pgp and gnupg.
I've downloaded postfix-2.9.4.tar.gz, postfix-2.9.4.tar.gz.sig,
wietse.pgp and I'm trying to verify the tarball signature.
I've taken the following steps (which I found at -
http://www.itmission.org/Main/How-to-verify-signature-of-dow
O.K., thank you.
So, I guess, gnupg won't verify an RSA key?
Perhaps FreeBSD needs a different program other than gnupg or pgp to
verify this type of signature? How do most people verify the package
signature?
Ed
Will,
I *think* I have the key added to my keyring - isn't that what the:
gpg --import wietse.pgp
does???
Ed
Solved! It WAS a bad download. I downloaded both the tarball and the
.sig file and got the following:
gpg: Signature made Wed Aug 1 15:14:44 2012 PDT using RSA key ID C12BCD99
gpg: Good signature from "Wietse Venema "
gpg: WARNING: This key is not certified with a trusted signature!
gpg:
I'm new to Postfix (I'll admit) and I'm trying to be a diligent user,
so I've looked at the INSTALL file and some of the README files, but I
don't see anything that looks like a possible solution to my problem.
Do I need to pass Postfix a parameter telling it what type of OS I
have before it will
Wow...thank you Wietse!
I *think* I know how to apply this, but can someone confirm this for me -
I think I can just copy and paste your code into a file, name it, and then:
patch –p0 < /path/to/patch/patch_name.patch
Right so far?
What file am I applying the patch to? The "makedefs" file, rig
Solved!
With the help of a co-worker, I used the -l parameter of patch to get
it to ignore whitespace. Prior to that, I kept getting hunk failures.
The command I used is:
patch –Cl –p0 < patch_name.patch
first to "Check" for errors and then just
patch –l –p0 < patch_name.patch.
Thank you Wiets
