SHA512, SHA384, SHA256, SHA1

Okay, let me sign the gpg2.1 man page (formatted so I can find things):
I actually have scripts to do a lot of this so here is the actual command in the script:

${GPG} –default-key ${KEYID} –output ${FILE}.sig –detach-sign $FILE

Here are the scripts:

http://www.SecureMecca.com/public/GnuPG-Scripts.7z
http://www.SecureMecca.com/public/GnuPG-Scripts.zip

The scripts saves on typing. Okay, what HASH did I use? Since the default is I am using MY key I don’t care what somebody else can handle (nobody has complained but in reality for a long time I have had it as SHA1 first just to avoid the complaints):

$ gpg2 -v –verify gpg2.1.sig
gpg: assuming signed data in `gpg2.1′
gpg: Signature made Wed 26 May 2010 06:15:36 AM UTC using RSA key ID 954D820D
gpg: using PGP trust model
gpg: Good signature from “Henry Hertz Hobbit ”
gpg: aka “Henry Hertz Hobbit ”
gpg: aka “Henry Hertz Hobbit ”
gpg: binary signature, digest algorithm SHA512

It is done this way in the example you gave because when you are signing a message sent to you it follows what you asked for. You want SHA-512 first so that is what it gave you. You can over-ride it with an explicit –digest-algo but I would not do it because it violates the OpenPGP standard. Give the actual command you use to clear-sign a file and people (others, not me) will better be able to help you. I assume you already answered this for yourself by now.

default-preference-list TWOFISH AES256 AES192 AES BLOWFISH 3DES SHA512 SHA384 SHA256 SHA224 SHA1 BZIP2 ZLIB ZIP Uncompressed
personal-cipher-preferences TWOFISH AES256 AES192 AES BLOWFISH 3DES
personal-digest-preferences SHA512 SHA384 SHA256 SHA224 SHA1
personal-compress-preferences ZLIB BZIP2 ZIP Uncompressed
cert-digest-algo SHA512

showpref
Cipher: TWOFISH, AES256, AES192, AES, BLOWFISH, 3DES
Digest: SHA512, SHA384, SHA256, SHA224, SHA1
Compression: BZIP2, ZLIB, ZIP, Uncompressed
Features: MDC, Keyserver no-modify

I didn’t consider the virus/malware possibility and didn’t have the time for more than a cursory glance at the source at the point when it occurred.

This popup is new to me, and it only appears on your site (thus far), although I’ve heard that Silverlight sites produce similar notifications. You’d think Microsoft wouldn’t link to everyone else’s browsers, though, if they were the source. The screenshot is available, since it is IE 6 we’re running, just tell me where you want it sent.

Thank you for the details on Chrome, I’ll credit you when I send the request.

Further, while I strive for standards as much as possible with this site, I make no guarantees that it will work in any browser, including text-based. However, just pulling up links2 in my terminal, and browsing the site, it seems to render rather well, and is quite readable and navigational.

Lastly, Chrome is using the rendering agent from Safari, namely KHTML. The UserAgent string identifies itself as Safari running on a Macintosh, not Google Chrome running on Windows. If this bothers you, I would suggest getting in touch with the Google Chrome development team, and submit a feature request for getting the UserAgent string changed.

Beyond that the blog was really good.

I think however gpg recently changed the way they decide on what cipher and hash to use. I think actually the personal-cipher-preference and personal-hash-preference are given priority over the recipients preferences embedded in their keys. (Please note I believe the old style way was to give priority to the preferences contained in the keys and then cross-reference the priorities with personal preferences when available.) Also note this process is much more complicated than described above, particularly if you are sending mail for example to 3 recipients each with different algorithms specified in their keys. You may actually want to discuss how this conundrum is handled since I find it interesting (however it might bore many users).