Ah sorry ... forgot to say. I'm running Windows 7. Final version. Got it through my MSDN subscription.
Using version 3.5.2 of Firefox.
1 2009-08-22 22:54:40
Re: Signing problem with 2048 bit DSA / 4096 bit ELG-E cert. (7 replies, posted in Bugs & problems)
2 2009-08-22 08:11:21
Re: Signing problem with 2048 bit DSA / 4096 bit ELG-E cert. (7 replies, posted in Bugs & problems)
Cool ... how could you spot that?
Firefox is set to use UTF-8 and gmail "Use default text encoding for outgoing messages" is set to "Use default text encoding for outgoing messages"
Should I change that to UTF-8 as well ?? Or change the firefox setting?
3 2009-08-21 16:56:00
Re: Signing problem with 2048 bit DSA / 4096 bit ELG-E cert. (7 replies, posted in Bugs & problems)
First ... what you asked for:
Output of a clearsign (with the strong DSA/ELG). I used old gmail and clearsign button, to clearsign the message:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
test af clearsign with STRONG cert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.8)
iF4EAREIAAYFAkqOtEIACgkQSAg8lmX8PLPRaAEA0AXW2hahgETszuQcjQ/dFEBP
SlSNlLxtrjWsyYY/srEBAIlTl+0fkZNkXM/pzNuKgR3jvNZyfKTwVyN8rD4dDixL
=9F/s
-----END PGP SIGNATURE-----
- The FireGPG texteditor is able to verify it just fine,
- But if I mark and and select "verify" from the FireGPG menu I get the following error:
"This message cannot be verified"
Now - if I instead select the same text, and use the "clearsign" command from the dropdown menu, I get this:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
stærk cert
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.8)
iF4EAREIAAYFAkqOwIsACgkQSAg8lmX8PLNQnAD/SZfNEON6GlMQs1HkFzbGRmdT
Uw4hjKphLCUstBobiRIA/1CxZPwbBnMOeEyos4B0TNqoe/McnzkSbQ9V73zqzUpt
=F44a
-----END PGP SIGNATURE-----
An I am able to verify that signature, from BOTH the dropdown "verify" and the Textbox verify button.
Do you understand what I mean? It's more than you asked for, but I thought that might help.
I haven't tried clearsigning untill now, but saw the behavior after a little testing. Again - It's repreducable on my machine.
I've tried to use the correct terms, but are new to the app, so I hope I got the message through 
4 2009-08-20 17:57:22
Topic: Signing problem with 2048 bit DSA / 4096 bit ELG-E cert. (7 replies, posted in Bugs & problems)
Hi,
I have installed GPG4Win 2.0, and I am using FireGPG for my gmail account. I do not use inline.
I created a certificate using Kleopatra and through the advanced setting I set the keys to be stronger, than the standard 1024 bit for both DSA and ELG-E.
I can not get signature verification to work with the certificate. I've tried deleting and creating a new one - same problem over again.
Signing and encryption and decryption goes well ... signature verification gives this results:
When certifying the signature I get "Unknown error, FireGPG can't verify this email"
I have no problem getting it to work with with a cert. with DSA/ELG cert 1024 bit keys. And a 4096 bit strong RSA key works fine as well.
The GPG4Win and FireGPG are default installations. Only thing I've changed is to get FireGPG to ask me which certificate I want to use.
Is this a known problem? Or is it something with my machine?