Re: 2.0.20 beta available
On Sat, 4 May 2013 00:15, a...@guardianproject.info said: > Oh, it must be not implemented in just 2.1 (git master). I just assumed > it wasn't implemented in 2.0 either. I wonder why it was removed from 2.1. In 2.1 the secret keys are manage by gpg-agent and in theory gpg should not care about them. However, we also have import and export commands which tell the agent what to do with the secret keys (i.e. import or export). A delete command is a bit more difficult regarding the UI because it is possible that gpgme uses the same secret key for an X.509 certificate - it would then also be silently deleted. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 2.0.20 beta available
Pete Stephenson: > On 5/2/2013 8:06 PM, Abel Luck wrote: >> Is it planned to support --delete-secret-keys? > > Do existing versions not support --delete-secret-keys? > Oh, it must be not implemented in just 2.1 (git master). I just assumed it wasn't implemented in 2.0 either. I wonder why it was removed from 2.1. ~abel > I've been using 2.0.17 and 2.0.19 on both Linux and Windows and have had > no issues with --delete-secret-keys. It seems to have worked for me: I > moved several secret keys over to smartcards (after making offline, > secure backups, of course), deleted the secret keys from the keyring, > and gnupg created the appropriate stubs pointing to the smartcard > without any issues. > > Cheers! > -Pete > > ___ > Gnupg-users mailing list > Gnupg-users@gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users > ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 2.0.20 beta available
On 5/2/2013 8:06 PM, Abel Luck wrote: > Is it planned to support --delete-secret-keys? Do existing versions not support --delete-secret-keys? I've been using 2.0.17 and 2.0.19 on both Linux and Windows and have had no issues with --delete-secret-keys. It seems to have worked for me: I moved several secret keys over to smartcards (after making offline, secure backups, of course), deleted the secret keys from the keyring, and gnupg created the appropriate stubs pointing to the smartcard without any issues. Cheers! -Pete ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 2.0.20 beta available
Is it planned to support --delete-secret-keys? ~abel Werner Koch: > Hi, > > it is now more than a year since we released 2.0.19. Thus it is really > time to get 2.0.20 out of the door. If you want to quickly try a beta > you may use: > > ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-2.0.20-beta118.tar.bz2 > > Please send bug reports only to the mailing list. > > > Noteworthy changes in version 2.0.20 (unreleased) > - > > * The hash algorithm is now printed for sig records in key listings. > > * Decryption using smartcards keys > 3072 bit does not work. > > * New meta option ignore-invalid-option to allow using the same >option file by other GnuPG versions. > > * [gpg] Skip invalid keyblock packets during import to avoid a DoS. > > * [gpg] Correctly handle ports from DNS SRV records. > > * [gpg-agent] Avoid tty corruption when killing pinentry. > > * [scdaemon] Rename option --disable-keypad to --disable-pinpad. > > * [scdaemon] Better support for CCID readers. Now, the internal CCID >driver supports readers without the auto configuration feature. > > * [scdaemon] Add pinpad input for PC/SC, if your reader has pinpad >and it supports variable length PIN input, and you specify >--enable-pinpad-varlen option. > > * [scdaemon] New option --enable-pinpad-varlen. > > * [scdaemon] Install into libexecdir to avoid accidental execution >from the command line. > > > The code also builds for Windows and we plan to do a Gpg4win release > soon after 2.0.20. > > > Shalom-Salam, > >Werner > > ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 2.0.20 beta available
On Thu, 25 Apr 2013 01:11, jhar...@widomaker.com said: > I don't see a .sig, so do these hashes (SHA1, SHA256) look correct? It is now there. > > 4dafebee7b0c7adde2b27473faca7236851cf472 > 72af477e33b15baf6733af3e5e5c49c18ddf398b8a90e93c65d04cb34f04f00b > 4277493 ./alpha/gnupg/gnupg-2.0.20-beta118.tar.bz2 sha1-looks fine: 4dafebee7b0c7adde2b27473faca7236851cf472 gnupg-2.0.20-beta118.tar.bz2 Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. pgpiUVEz6T_bU.pgp Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 2.0.20 beta available
On Wed, 24 Apr 2013 23:04, da...@systemoverlord.com said: > * Decryption using smartcards keys > 3072 bit does not work. s/not/now/ Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 2.0.20 beta available
On Wed, Apr 24, 2013 at 09:40:51PM +0200, Werner Koch wrote: > Hi, > > it is now more than a year since we released 2.0.19. Thus it is really > time to get 2.0.20 out of the door. If you want to quickly try a beta > you may use: > > ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-2.0.20-beta118.tar.bz2 > > Please send bug reports only to the mailing list. I don't see a .sig, so do these hashes (SHA1, SHA256) look correct? 4dafebee7b0c7adde2b27473faca7236851cf472 72af477e33b15baf6733af3e5e5c49c18ddf398b8a90e93c65d04cb34f04f00b4277493 ./alpha/gnupg/gnupg-2.0.20-beta118.tar.bz2 Thanks. -- Jason Harris | PGP: This _is_ PGP-signed, isn't it? jhar...@widomaker.com _|_ Got photons? (TM), (C) 2004 pgpE_07nLZ9le.pgp Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: 2.0.20 beta available
Hi Werner, A question about the release notes: * Decryption using smartcards keys > 3072 bit does not work. Is this a regression (since it's listed as a change) or should it read "does now work"? I don't have any 4k keys on smartcards to try with, but I'm interested to know the status. Thanks, David On Wed, Apr 24, 2013 at 12:40 PM, Werner Koch wrote: > Hi, > > it is now more than a year since we released 2.0.19. Thus it is really > time to get 2.0.20 out of the door. If you want to quickly try a beta > you may use: > > ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-2.0.20-beta118.tar.bz2 > > Please send bug reports only to the mailing list. > > > Noteworthy changes in version 2.0.20 (unreleased) > - > > * The hash algorithm is now printed for sig records in key listings. > > * Decryption using smartcards keys > 3072 bit does not work. > > * New meta option ignore-invalid-option to allow using the same >option file by other GnuPG versions. > > * [gpg] Skip invalid keyblock packets during import to avoid a DoS. > > * [gpg] Correctly handle ports from DNS SRV records. > > * [gpg-agent] Avoid tty corruption when killing pinentry. > > * [scdaemon] Rename option --disable-keypad to --disable-pinpad. > > * [scdaemon] Better support for CCID readers. Now, the internal CCID >driver supports readers without the auto configuration feature. > > * [scdaemon] Add pinpad input for PC/SC, if your reader has pinpad >and it supports variable length PIN input, and you specify >--enable-pinpad-varlen option. > > * [scdaemon] New option --enable-pinpad-varlen. > > * [scdaemon] Install into libexecdir to avoid accidental execution >from the command line. > > > The code also builds for Windows and we plan to do a Gpg4win release > soon after 2.0.20. > > > Shalom-Salam, > >Werner > -- David Tomaschik OpenPGP: 0x5DEA789B http://systemoverlord.com da...@systemoverlord.com ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
2.0.20 beta available
Hi, it is now more than a year since we released 2.0.19. Thus it is really time to get 2.0.20 out of the door. If you want to quickly try a beta you may use: ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-2.0.20-beta118.tar.bz2 Please send bug reports only to the mailing list. Noteworthy changes in version 2.0.20 (unreleased) - * The hash algorithm is now printed for sig records in key listings. * Decryption using smartcards keys > 3072 bit does not work. * New meta option ignore-invalid-option to allow using the same option file by other GnuPG versions. * [gpg] Skip invalid keyblock packets during import to avoid a DoS. * [gpg] Correctly handle ports from DNS SRV records. * [gpg-agent] Avoid tty corruption when killing pinentry. * [scdaemon] Rename option --disable-keypad to --disable-pinpad. * [scdaemon] Better support for CCID readers. Now, the internal CCID driver supports readers without the auto configuration feature. * [scdaemon] Add pinpad input for PC/SC, if your reader has pinpad and it supports variable length PIN input, and you specify --enable-pinpad-varlen option. * [scdaemon] New option --enable-pinpad-varlen. * [scdaemon] Install into libexecdir to avoid accidental execution from the command line. The code also builds for Windows and we plan to do a Gpg4win release soon after 2.0.20. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
