I can understand your reasoning, it makes sense.
May 1 2018
Feb 2 2018
Jan 18 2018
Jan 17 2018
Nov 11 2016
Thanks a lot. I will test as soon as you release the test build.
Aug 12 2016
The Kaspersky issue is about Outlook 2007... Is that supposed bug really already
Jul 13 2016
To make it clear: I'm not even trying to sign or encrypt, just send a plaintext
message with attachment also in the clear.
Oct 25 2013
Sorry for being ignorant, but I don't even know what gpgsm is... ;-)
I'm just using the "classical" gpg since it came into life (being a PGP user for
more than 20 years now)...
But since gpgsm seems to use a separate directory for the private keys it's fine
for me as well -- I will then mount that directory as an encrypted one...
Oct 23 2013
Does that mean there will only be a single keyring in the future? So that I can
not lock-away my secret key(s) while I don't need them?
Oct 15 2013
Used the latest MacPorts version available as of today.
Now the picture changed somewhat:
- 8x -----------
$ gpg2 --delete-keys 450F89EC
gpg (GnuPG) 2.0.21; Copyright (C) 2013 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
gpg: keyblock resource `/Users/theUser/Documents/Encrypted/gpg/secring.gpg': No
such file or directory
pub 1024D/450F89EC 2003-02-03 PAUSE Batch Signing Key 2011 <firstname.lastname@example.org>
Delete this key from the keyring? (y/N) y
- 8x -----------
As you see gpg2 STILL for whatever reason tries to do "something" with the
secret keyring (even though I would not expect this since the command supposedly
only operates on PUBLIC keys), but this time it succeeds.
So this is only a minor annoyance, but still I consider it "quirkish."