Re: [EXT] Best practices for obtaining a new GPG certificate

Hi David, when Gentoo switched to requiring gpg-signed git commits and pushes, we put some thought into requirements and best practices. Minus the Gentoo-specific parts, this is probably good reading: https://www.gentoo.org/glep/glep-0063.html https://wiki.gentoo.org/wiki/Project:Infrastructur

Re: [EXT] Re: gnupg and ssh interaction somehow broken (card reader with pinpad)

> > Can you swap the readers between the two computers and see if the > problem follows the suspected-bad reader? > Possible as last resort, I'd rather figure this out some other way though. -- PD Dr. Andreas K. Huettel Institute for Experimental and Applied Physics University of Regensburg 93

Re: [EXT] Best practices for obtaining a new GPG certificate

On 3/18/2021 10:21 AM, Andreas K. Huettel wrote: Hi David, when Gentoo switched to requiring gpg-signed git commits and pushes, we put some thought into requirements and best practices. Minus the Gentoo-specific parts, this is probably good reading: https://www.gentoo.org/glep/glep-0063.html ht

Re: [EXT] Best practices for obtaining a new GPG certificate

https://www.gentoo.org/glep/glep-0063.html https://wiki.gentoo.org/wiki/Project:Infrastructure/Generating_GLEP_63_based_OpenPGP_keys > On the pages, I get 'There is currently no text in this page. You can > search for this page title in other pages, or ...'. > Am I missing something? Only that km

Re: gnupg and ssh interaction somehow broken (card reader with pinpad)

On Wed, 17 Mar 2021 16:31, Andreas K. Huettel said: > 2021-03-17 16:15:37 scdaemon[4932] Prüfung des CHV1 fehlgeschlagen: > Ungültiger > [Not being familiar with the details, I dont know if I can post the full log > here or if it contains sensitive data.] At that debug level it is okay. Howeve

Re: [EXT] Best practices for obtaining a new GPG certificate

On 3/18/2021 2:39 PM, Andreas K. Huettel wrote: https://www.gentoo.org/glep/glep-0063.html https://wiki.gentoo.org/wiki/Project:Infrastructure/Generating_GLEP_63_based_OpenPGP_keys Reading the URLs given by the OP, I see that the GPG FAQ (1) talks about a default of '2048' but in the latest (2

Re: Best practices for obtaining a new GPG certificate

On Thu, 18 Mar 2021 00:06, David Mehler said: > My existing GPG certificate is going to expire in less than a month. > I'd like to know current best practices for obtaining a new one? In Do you really want a new one? Usually it is easier to prolong your key. By default a new key has an expire da

Timeout when signing

Hi, I'm trying to encrypt and sign a large file. It takes a while to do this, and I then do other things while this is happening. It then completes and presumably asks me for my key passphrase, but I miss this and it times out, so all I see is the following error message: gpg: signing failed: Tim

Re: Best practices for obtaining a new GPG certificate

Hello, Thanks all. I am definitely wanting a new key. With regards the info John posted: gpg --expert --full-gen-key Please select what kind of key you want:    (1) RSA and RSA (default)    (2) DSA and Elgamal    (3) DSA (sign only)    (4) RSA (sign only)    (7) DSA (set your own capabilities)  

Re: Timeout when signing

On 2021-03-18 at 13:57 +, Nick Cripps via Gnupg-users wrote: > Hi, > > I'm trying to encrypt and sign a large file. It takes a while to do > this, and I then do other things while this is happening. It then > completes and presumably asks me for my key passphrase, but I miss > this and it time

Re: [EXT] Best practices for obtaining a new GPG certificate

On 2021-03-18 at 15:15 +0100, john doe via Gnupg-users wrote: > Reading the URLs given by the OP, I see that the GPG FAQ (1) talks > about a default of '2048' but in the latest (2.2.17) release of GPG > it looks like the default is now '3072': > What keysize do you want? (3072) > > > Am I missing