Decrypting fails unless card status

2020-12-14 Thread Felix E. Klee
Since some time, maybe since a minor system update, before decrypting from my OpenPGP smart card, I always have to run: gpg --card-status Otherwise, I get an error message: $ gpg --faked-system-time 20200101T00 -d world.gpg gpg: WARNING: running with faked system time:

Re: [Keyserver] Hockeypuck 2.1.0 released

2020-12-14 Thread Stefan Claas via Gnupg-users
On Mon, Dec 14, 2020 at 5:24 PM Casey Marshall via Gnupg-users wrote: >> [...] > The fix to this issue was to have Hockeypuck remove all packets lacking a > currently-valid self-signature from responses. This removes fake packets > (like the uat example) as well as expired identities. The

Re: [Keyserver] Hockeypuck 2.1.0 released

2020-12-14 Thread Casey Marshall via Gnupg-users
> > Date: Fri, 11 Dec 2020 17:56:24 + > From: Stefan Claas > To: Casey Marshall via Gnupg-users , > sks-de...@nongnu.org, Casey Marshall > Subject: Re: [Keyserver] Hockeypuck 2.1.0 released > Message-ID: > < >

Re: Protecting your private key - passphrase

2020-12-14 Thread Stefan Claas via Gnupg-users
On 2020-12-14 12:26, Robert J. Hansen via Gnupg-users wrote: >> People who have difficulties to create a long passphrase and >> remembering those, when using differrent ones for different use cases. > > Then why aren't you using PBKDF2 or Argon2? > > If you're writing a key derivation app -- use

Re: Best practice to use several smartcards for a single key?

2020-12-14 Thread m.fernandes.business via Gnupg-users
> > Date: Sun, 13 Dec 2020 21:22:44 + > From: Andrew Gallagher > Message-ID: <9ae37da2-0e50-46cd-8f16-05c4d55b3...@andrewg.com> > > > > On 13 Dec 2020, at 11:08, Nicolas Boullis > wrote: > > > > My idea was that there was little chance that a smartcard fails (Werner > > Koch told me that the

Re: Protecting your private key - passphrase

2020-12-14 Thread Robert J. Hansen via Gnupg-users
People who have difficulties to create a long passphrase and remembering those, when using differrent ones for different use cases. Then why aren't you using PBKDF2 or Argon2? If you're writing a key derivation app -- use a key derivation function. Had I used PBKDF2 for my litle program

Re: Protecting your private key - passphrase

2020-12-14 Thread Robert J. Hansen via Gnupg-users
you are one hundred percent correct that the output of my programs are *not* random and that they do not generate random output like a CSPRNG does. I'm not going to discuss this with you further. It's clear you don't know what you're doing, and I trust that's been made clear to the mailing

Re: Protecting your private key - passphrase

2020-12-14 Thread Werner Koch via Gnupg-users
Hi! Let me also add that the private key protection mechanism of OpenPGP does not work like we would do it these days. Thus my suggestion has always been: If you need to convey a private key over a public channel do not rely on the passphrase protection [1] but wrap the backuped key in a proper

Re: Protecting your private key - passphrase

2020-12-14 Thread Stefan Claas via Gnupg-users
Robert, you are one hundred percent correct that the output of my programs are *not* random and that they do not generate random output like a CSPRNG does. So, once again, I appologize for my wrong wording and should had better used garbled looking output, compared to a regular users passphrase

Re: Protecting your private key - passphrase

2020-12-14 Thread Stefan Claas via Gnupg-users
On Mon, Dec 14, 2020 at 5:35 AM Robert J. Hansen wrote: > > > I guess you have not read my initial posting ... otherwise you would > > think different and would not say so ... > > Stefan, I read your original posting and I completely concur with Ingo. > > > The program is not only for GnuPG usage