Re: Reviving a userid with revoked key

2017-05-19 Thread Michael Englehorn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Marc Curry writes: > 1) was at a company (e.g. m...@company-a.com) > 2) went to company-b and revoked key for marc@company-a > 3) now I'm back at company-a, and want to start using m...@company-a.com > userid again If you

Re: Reviving a userid with revoked key

2017-05-19 Thread Kristian Fiskerstrand
On 05/19/2017 08:36 PM, Marc Curry wrote: > Maybe a dumb question, but I'm looking for help thinking through how to > best "revive" an old gpg key's userid after I revoked it a few years ago, > thinking I wouldn't need to use it, again. > > 1) was at a company (e.g. m...@company-a.com) > 2) went

Reviving a userid with revoked key

2017-05-19 Thread Marc Curry
Maybe a dumb question, but I'm looking for help thinking through how to best "revive" an old gpg key's userid after I revoked it a few years ago, thinking I wouldn't need to use it, again. 1) was at a company (e.g. m...@company-a.com) 2) went to company-b and revoked key for marc@company-a 3) now

Re: Did exit codes change in 2.1.21?

2017-05-19 Thread Philip Jocks
Hej, > Here is my fix: > https://dev.gnupg.org/rGa8dd96826f8484c0ae93c954035b95c2a75c80f2 > > Please try this patch. seems to work. Now the exit code is 0 again, as expected. When building without SCDAEMON support, I get gpg: WARNING: server 'scdaemon' is older than us ((null) < 2.1.21)