Re: Key expiration question

2017-06-15 Thread listo factor via Gnupg-users
On 06/13/2017 01:02 PM, Peter Lebbing wrote: An expired key will definitely not be able to issue valid signatures after the expiration date. There is nothing ~in the key itself~ that prevents any key from being used to create signatures, it is only a feature of the software used to create the

Re: modern GnuPG verify signatures

2017-06-15 Thread Stefan Claas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 15 Jun 2017 23:29:41 +0300 Teemu Likonen wrote: > Stefan Claas [2017-06-15 18:59:41+02] wrote: > > > I clearsign a text file and verify it and modern GnuPG shows me this: > > > > gpg --verify my_message.txt > > gpg: Signature made Do 15 Ju

Re: modern GnuPG verify signatures

2017-06-15 Thread Teemu Likonen
Stefan Claas [2017-06-15 18:59:41+02] wrote: > I clearsign a text file and verify it and modern GnuPG shows me this: > > gpg --verify my_message.txt > gpg: Signature made Do 15 Jun 18:31:05 2017 CEST > gpg:using RSA key 2BAF85F9281ABD543823C7C5981EB7C382EC52B4 > gpg: Good signature

Re: modern GnuPG verify signatures

2017-06-15 Thread Stefan Claas
Am 15.06.17 um 19:36 schrieb Stefan Claas: > > Am 15.06.17 um 18:59 schrieb Stefan Claas: > > > I will now also sign my message and hope i don't mess this post up, > > so that you can verify my sig and tell me if it shows you also the > > long-key ID or full key on your system. > ... just in case a

Re: modern GnuPG verify signatures

2017-06-15 Thread Stefan Claas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am 15.06.17 um 18:59 schrieb Stefan Claas: > I will now also sign my message and hope i don't mess this post up, > so that > you can verify my sig and tell me if it shows you also the > long-key ID or full key on your system. > ... just in case an

Re: modern GnuPG verify signatures

2017-06-15 Thread Stefan Claas
Am 15.06.17 um 17:49 schrieb Peter Lebbing: > On 15/06/17 17:24, Stefan Claas wrote: >> when i sign a message and do a gpg --verify it shows "using RSA >> key 2BAF85F9281ABD543823C7C5981EB7C382EC52B4", in Terminal under >> macOS, with my own key, but when doing the verify again with a >> message fr

Re: Behaviour of gpgsm / gpgme with multiple S/MIME certificates/keys per address (old/expired/about to expire and new)

2017-06-15 Thread Dr. Thomas Orgis
Am Fri, 9 Jun 2017 14:17:24 +0200 schrieb "Dr. Thomas Orgis" : > But after that, claws-mail as well as gpgsm complain about > the keys being ambiguous. Clearly, the call No takers? I am the only one getting a fresh S/MIME cert? I now modified claws-mail to add preferences to each mail account f

Re: modern GnuPG verify signatures

2017-06-15 Thread Peter Lebbing
On 15/06/17 17:24, Stefan Claas wrote: > when i sign a message and do a gpg --verify it shows "using RSA > key 2BAF85F9281ABD543823C7C5981EB7C382EC52B4", in Terminal under > macOS, with my own key, but when doing the verify again with a > message from someone else it shows the long key-ID, instead

modern GnuPG verify signatures

2017-06-15 Thread Stefan Claas
Hi all, when i sign a message and do a gpg --verify it shows "using RSA key 2BAF85F9281ABD543823C7C5981EB7C382EC52B4", in Terminal under macOS, with my own key, but when doing the verify again with a message from someone else it shows the long key-ID, instead of the full key. Is this a bug? Rega

How to use a PKCS#15 with GnuPG?

2017-06-15 Thread NdK
Hello all. I'm trying to use an ePass2003 token (and possibly some Aventra MyID cards) to have my keys around when I need 'em (especially for authentication and signing). Both ePass2003 and MyID implement PKCS#15, so IIUC they should be usable. Too bad I can't find the needed infos... I generated