Robert, So, should I convert to the gpg2 format "/within/ the old GnuPG directory" (1) or install gpg2 in parallel to gpg1 (2), as described in these two Webpages?
1) "The proposed migration path to the new keybox format is converting /within/ the old GnuPG directory rather than moving to a completely new one," https://superuser.com/questions/1093683/new-gnupg-directory-import-old-secret-keys-into-new-install#1093692 2) "Update 2017-07-09 If you are resurrecting an old gpg key created when gpg1 was in use (these days gpg2 is in use)", https://sites.google.com/site/nandydandyoracle/scst/update-gpg-key-email-address-for-signing-debian-packages#TOC-Download-the-Key Thanks, Thomas > ------------------------------ > > Message: 3 > Date: Sun, 26 Aug 2018 16:11:49 -0400 > From: "Robert J. Hansen" <r...@sixdemonbag.org> > To: enigmail-users@enigmail.net > Subject: Re: [Enigmail] Need the secret key to do this (extend the > expiration date). > Message-ID: <3edde3ec-f539-4722-49e6-b0d05f507...@sixdemonbag.org> > Content-Type: text/plain; charset=utf-8 > >> Thomas F. Ruddy: >>> I am running GPG version 1 on Linux Mint KDE. > Okay. > >>> So when I compare my results via the commandline with those attained >>> through Enigmail, I wonder whether Enigmail will update the trustdb >>> eventually; now I see that: > Not okay. > > Enigmail can only use GnuPG 2, not GnuPG 1, and depending on which GnuPG > 2 version you're using, it may use a different keyring altogether -- so > any changes made via GnuPG 1 may not be reflected in Enigmail, and vice > versa. > > Flapflap, > So you succeeded to extend the expiration date of the key and upload it > and it only doesn't show up in Enigmail?! No, the other way around: Enigmail shows the new expiration date, and even uploads; but what is uploaded shows the old expiration date. So today I tried this: I consciously used root to extend my expiration date. Everything worked, but the upload is now forbidden along with the warning that my configuration file `/home/thomas/.gnupg/gpg.conf' is said to have unsafe ownership. I even exported the new key to a file publickey.asc I am not convinced that the "unsafe ownership" is significant. Could I not just use the new file? I could email it to a friend to try out. Thomas On 08/26/2018 10:05 PM, flapflap wrote: > Hi Thomas, > > Thomas F. Ruddy: >> I am running GPG version 1 on Linux Mint KDE. >> >> When I try to extend the expiration date of my public key, I get >> >> gpg> expire >> Need the secret key to do this. >> >> ...and despite the advice given on various Webpages, no box appears for >> me to input my secret key's passphrase. >> >> This question has come up on various Webpages, but no coherent answer >> was ever given to my knowledge. >> >> Enigmail indeed will extend expiration, but it fails to upload its >> results to a keyserver such as pgp.mit.edu > I'm unsure how far you have gotten. What you wrote contradicts a bit... > Either you've failed to extend the expiration date of your key, or you > didn't. Either you could upload the updated key to the keyservers, or > you couldn't. > >> So when I compare my results via the commandline with those attained >> through Enigmail, I wonder whether Enigmail will update the trustdb >> eventually; now I see that: >> >> gpg: next trustdb check due at 2018-09-01 >> >> i.e. the day when my public key will expire. > So you succeeded to extend the expiration date of the key and upload it > and it only doesn't show up in Enigmail?! If that's your problem you can > simpliy do: > > Enigmail > Key Management > File > Reload Key Cache > > HTH, > ~flapflap On 08/27/2018 12:01 PM, enigmail-users-requ...@enigmail.net wrote: > Send enigmail-users mailing list submissions to > enigmail-users@enigmail.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net > > or, via email, send a message with subject or body 'help' to > enigmail-users-requ...@enigmail.net > > You can reach the person managing the list at > enigmail-users-ow...@enigmail.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of enigmail-users digest..." > > > Today's Topics: > > 1. Need the secret key to do this (extend the expiration date). > (Thomas F. Ruddy) > 2. Re: Need the secret key to do this (extend the expiration > date). (flapflap) > 3. Re: Need the secret key to do this (extend the expiration > date). (Robert J. Hansen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 26 Aug 2018 19:10:12 +0200 > From: "Thomas F. Ruddy" <tho...@thomasruddy.org> > To: enigmail-users@enigmail.net > Subject: [Enigmail] Need the secret key to do this (extend the > expiration date). > Message-ID: <8c688cd3-5abf-67a8-9767-c3a0232cb...@thomasruddy.org> > Content-Type: text/plain; charset=utf-8 > > I am running GPG version 1 on Linux Mint KDE. > > When I try to extend the expiration date of my public key, I get > > gpg> expire > Need the secret key to do this. > > ...and despite the advice given on various Webpages, no box appears for > me to input my secret key's passphrase. > > This question has come up on various Webpages, but no coherent answer > was ever given to my knowledge. > > Enigmail indeed will extend expiration, but it fails to upload its > results to a keyserver such as pgp.mit.edu > > So when I compare my results via the commandline with those attained > through Enigmail, I wonder whether Enigmail will update the trustdb > eventually; now I see that: > > gpg: next trustdb check due at 2018-09-01 > > i.e. the day when my public key will expire. >
_______________________________________________ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
