Posted on Flyspray at FS#295
1 2009-05-26 11:25:26
Re: Automatic private key selection not working, error on manual (3 replies, posted in Bugs & problems)
2 2009-05-26 11:12:13
Re: Automatic private key selection not working, error on manual (3 replies, posted in Bugs & problems)
1) I'll file it there.
2) Yes. Sounds like it should be an easy fix, then.
3 2009-05-26 10:38:01
Topic: Automatic private key selection not working, error on manual (3 replies, posted in Bugs & problems)
I have two private keys, one for my personal email addresses and another for my day job address. There's no overlap on which addresses the keys cover.
I've had the personal key set as default for a long time now but only just realized that all mail, even that from the day job address, is being signed with the personal key.
Now, if I set the default key to "always ask", the dialog pops up when I try to send a message asking which key I want to use. Interestingly, the correct key is always highlighted -- the personal one if I'm using my personal email addresses and the day job one if the from address is set to my day job address. I click OK and type the passphrase but then get this error:
Signing failed because of an unknown error. Make sure a default private key has been set in the preferences.
gpg: no default secret key: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
A default private key would be just fine if it didn't then sign /all/ mail with that key, as described above. Something's going wrong here.
Thanks
4 2009-04-07 13:21:40
Re: Attached signature with non-base64 plaintext? (2 replies, posted in Requests)
1. Why not? Would you consider adding that feature? Every now and then I need to look at the raw email and it's good to be able to read (much of) the body without having to decode it first.
2. It isn't for me. FireGPG version 0.7.5
5 2009-04-07 12:22:04
Topic: Attached signature with non-base64 plaintext? (2 replies, posted in Requests)
Is there a way to have FireGPG send signed (attachment) emails with the body text encoded as quoted-printable rather than base64?
It also doesn't seem to automatically insert line breaks (every 74ish characters would be good). Is there a setting I'm missing?