Re: rm ~/.gnupg/secring NOW!

2017-08-04 Thread Daniel Pocock
On 03/08/17 18:19, Adam Borowski wrote: > On Thu, Aug 03, 2017 at 09:54:28AM +0100, Daniel Pocock wrote: >> On 02/08/17 21:30, Adam Borowski wrote: >>> On Wed, Aug 02, 2017 at 09:53:27PM +0200, Adam Borowski wrote: If you have ever generated or imported a gpg secret key using gpg 1 or 2.0

Re: rm ~/.gnupg/secring NOW!

2017-08-03 Thread Adam Borowski
On Thu, Aug 03, 2017 at 09:54:28AM +0100, Daniel Pocock wrote: > On 02/08/17 21:30, Adam Borowski wrote: > > On Wed, Aug 02, 2017 at 09:53:27PM +0200, Adam Borowski wrote: > >> If you have ever generated or imported a gpg secret key using gpg 1 or 2.0 > >> (ie, before Stretch), then used --delete-s

Re: rm ~/.gnupg/secring NOW!

2017-08-03 Thread Daniel Pocock
On 02/08/17 21:30, Adam Borowski wrote: > On Wed, Aug 02, 2017 at 09:53:27PM +0200, Adam Borowski wrote: >> If you have ever generated or imported a gpg secret key using gpg 1 or 2.0 >> (ie, before Stretch), then used --delete-secret-key, please >> rm ~/.gnupg/secring.gpg > Obviously, this assumes

Re: rm ~/.gnupg/secring NOW!

2017-08-02 Thread Adam Borowski
On Wed, Aug 02, 2017 at 09:53:27PM +0200, Adam Borowski wrote: > If you have ever generated or imported a gpg secret key using gpg 1 or 2.0 > (ie, before Stretch), then used --delete-secret-key, please > rm ~/.gnupg/secring.gpg Obviously, this assumes you did run a gpg command after upgrading from

rm ~/.gnupg/secring NOW!

2017-08-02 Thread Adam Borowski
Hi guys! Heads up: If you have ever generated or imported a gpg secret key using gpg 1 or 2.0 (ie, before Stretch), then used --delete-secret-key, please rm ~/.gnupg/secring.gpg (and shred/trim/balance/etc -- it's a huge topic). If you --delete-secret-key with gpg 2.1, it deletes the key only fro