[Enigmail] qualifizierte elektronische Signatur
Sehr geehrte Damen und Herren, ich versuche eine qualifizierte elektronische Signatur (QES) nach SigG in meine E-Mails einzubinden. Da ich bei Ihrem Thunderbird Add-On auch den Reiter "SmartCard" gefunden habe, stellt sich mir die Frage, ob Sie QES unterstützen. Wenn ja, benötige ich eine klassische Signaturkarte oder akzeptieren Sie auch den aktivierten nPA? Mit freundlichen Grüßen Frederik Pascal Genreith frederikpascalgenre...@yahoo.de signature.asc Description: OpenPGP digital signature ___ 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
[Enigmail] FAQ / Enigmail Gpg2 and "Missing passphrase" "No secret key" error
Hi, If your FAQ, on the webpage: https://www.enigmail.net/index.php/en/faq?view=category&id=11#faqLink_2 In the section "Resolving issues with GnuPG 2.x and gpg-agent" You forgot to talk about an error I just encountered, following the switch from gpg1x to gpg2x: my drafts were automatically encrypted, but each time I tried to re-edit them, I faced a violet banner with the error: Missing passphrase gpg: decryption failed: No secret key Thanks to a comment on the following webpage: http://stackoverflow.com/questions/91355/gnupg-decryption-failed-secret-key-not-available-error-from-gpg-on-windows#7974613 and some testing on a locally encrypted file, I finally managed to solve the problem: you have to do the export/import of the *secret* keys manually with: gpg --export-secret-keys > seckeysfile gpg2 --import seckeysfile shred -n 100 seckeysfile I'm not sure if I made a mistake when switching from gpg to gpg2, or if it is a bug in gpg2, or if there was a tool in enigmail to switch to gpg2, which forgot to export/import the secret keys, but I think it would save a lot of time to other people like me if you would mention the problem/solution in your FAQ! Cheers, -- Guillaume MULLER, PhD PRESANS - Remix Coworking - L'Appart 57 rue de Turbigo 75003 Paris France http://www.presans.com http://feeds.feedburner.com/OYI/fr ___ 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
[Enigmail] gpg2: problem with the agent: No pinentry? - Ask Fedora: Community Knowledge Base and Support Forum
Hi again, In fact, after verification, what worked was: --- If necessary, edit/create ~/.gnupg/gpg-agent.conf and add one of the following lines pinentry-program /usr/bin/pinentry-curses $ unset DISPLAY --- https://ask.fedoraproject.org/en/question/32052/gpg2-problem-with-the-agent-no-pinentry/ ___ 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
Re: [Enigmail] qualifizierte elektronische Signatur
Hi, On 01.09.16 14:14, Frederik Pascal Genreith wrote: > Sehr geehrte Damen und Herren, We're not so formal here on this mailing list ;-) And we're speaking in english. > ich versuche eine qualifizierte elektronische Signatur (QES) nach SigG > in meine E-Mails einzubinden. > Da ich bei Ihrem Thunderbird Add-On auch den Reiter "SmartCard" gefunden > habe, stellt sich mir die Frage, ob Sie QES unterstützen. Wenn ja, > benötige ich eine klassische Signaturkarte oder akzeptieren Sie auch den > aktivierten nPA? Well, Enigmail supports the OpenPGP standard using GnuPG as the crypographic backend. I don't think GnuPG supports QES as it seems to require specialized hardware and/or tokens. Your question is better suited for a GnuPG users mailing list, either international at gnupg-us...@gnupg.org, or, if you prefer german: gnupg...@gnupg.org HTH Ludwig signature.asc Description: OpenPGP digital signature ___ 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
Re: [Enigmail] FAQ / Enigmail Gpg2 and "Missing passphrase" "No secret key" error
On 01.09.16 14:42, Guillaume MULLER wrote: (...) > I'm not sure if I made a mistake when switching from gpg to gpg2, or > if it is a bug in gpg2, or if there was a tool in enigmail to switch > to gpg2, which forgot to export/import the secret keys, but I think > it would save a lot of time to other people like me if you would > mention the problem/solution in your FAQ! gpg1.x and gpg2.x should be able to operate on the _same_ keyrings. Which versions of gpg1.x and gpg2.x are you using exactly? Ludwig signature.asc Description: OpenPGP digital signature ___ 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
Re: [Enigmail] FAQ / Enigmail Gpg2 and "Missing passphrase" "No secret key" error
On 2016-09-01 at 14:42, Guillaume MULLER wrote: > I'm not sure if I made a mistake when switching from gpg to gpg2, or if it is > a bug in gpg2, or if there was a tool in enigmail to switch to gpg2, which > forgot to export/import the secret keys, but I think it would save a lot of > time to other people like me if you would mention the problem/solution in > your FAQ! > Versions of GnuPG modern branch (2.1.0 and later) use a different way to store private keys, so not all cases where you use `gpg2` will have that problem, if you have stable branch (2.0.x). Although it would be a QoL thing for Enigmail to add that, it was explained way back when 2.1.0 was released. Hopefully more and more distros reprecate the 'gpg' and 'gpg2' package mix, or follow Debian's way of having GnuPG 1.x as an optional package called 'gnupg1' while having GnuPG >=2.1 as 'gpg'. -- Juan Miguel Navarro Martínez GPG Keyfingerprint: 5A91 90D4 CF27 9D52 D62A BC58 88E2 947F 9BC6 B3CF ___ 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
[Enigmail] Have to killall and relaunch gpg-agent after every reboot..
Hi, Whenever I try to read an encrypted e-mail I get the following error message: "GnuPG cannot query your passphrase via pinentry. This is a system setup or configuration error that prevents Enigmail from working properly and cannot be fixed automatically. We strongly recommend that you consult our support web site at https://enigmail.net/faq."; The only way I found to make it work is to "killall gpg-agent" and relaunch it with "gpg-agent --debug-level expert --use-standard-socket --daemon /bin/sh" I get the following message by the way: gpg-agent[8221]: WARNING: "--use-standard-socket" is an obsolete option - it has no effect gpg-agent[8221]: enabled debug flags: command cache ipc gpg-agent[8221]: listening on socket '/run/user/1000/gnupg/S.gpg-agent' $ gpg-agent[8222]: gpg-agent (GnuPG) 2.1.15 started If I simply relaunch gpg-agent (without "--debug-level expert --use-standard-socket --daemon /bin/sh") Enigmail still doesn't work. Trying to add "use-standard-socket" to $HOME/.gnupg/gpg-agent.conf didn't make it (obsolete option...) Any idea ? Thanks Config: Ubuntu 16.04 Thunderbird 45.2.0 Enigmail 1.9.5 gpg 2.1.15 ___ 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
Re: [Enigmail] Have to killall and relaunch gpg-agent after every reboot..
On 01.09.16 21:25, acubene+enigm...@vivaldi.net wrote: > (...) > If I simply relaunch gpg-agent (without "--debug-level expert > --use-standard-socket --daemon /bin/sh") Enigmail still doesn't work. Some days another user had the same problem on Ubuntu 16.04. He solved it by starting over with a completely new .gnupg directory (and of course transferring keys and trust). > Trying to add "use-standard-socket" to $HOME/.gnupg/gpg-agent.conf > didn't make it (obsolete option...) > > Any idea ? Try to remove everything in gpg.conf and gpg-agent.conf except all entries which are absolutely necessary. Ludwig signature.asc Description: OpenPGP digital signature ___ 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
Re: [Enigmail] Have to killall and relaunch gpg-agent after every reboot..
OK thanks Ludwig I'll try that Le 01. 09. 16 à 22:06, Ludwig Hügelschäfer a écrit : > On 01.09.16 21:25, acubene+enigm...@vivaldi.net wrote: > >> (...) >> If I simply relaunch gpg-agent (without "--debug-level expert >> --use-standard-socket --daemon /bin/sh") Enigmail still doesn't work. > > Some days another user had the same problem on Ubuntu 16.04. He solved > it by starting over with a completely new .gnupg directory (and of > course transferring keys and trust). > >> Trying to add "use-standard-socket" to $HOME/.gnupg/gpg-agent.conf >> didn't make it (obsolete option...) >> >> Any idea ? > > Try to remove everything in gpg.conf and gpg-agent.conf except all > entries which are absolutely necessary. > > Ludwig > > > > > ___ > 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 > ___ 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
Re: [Enigmail] Have to killall and relaunch gpg-agent after every reboot..
Yes, that 'other user' was me. And a fresh gnupg install solved the dilemma, just imported the keyring and trustdb I had to remove one other file pubring.kbx, as it conflicts with the pubring.gpg Give it a try.. and report back Thomas On 09/01/2016 10:08 PM, acubene+enigm...@vivaldi.net wrote: > OK thanks Ludwig > I'll try that > > Le 01. 09. 16 à 22:06, Ludwig Hügelschäfer a écrit : >> On 01.09.16 21:25, acubene+enigm...@vivaldi.net wrote: >> >>> (...) >>> If I simply relaunch gpg-agent (without "--debug-level expert >>> --use-standard-socket --daemon /bin/sh") Enigmail still doesn't work. >> Some days another user had the same problem on Ubuntu 16.04. He solved >> it by starting over with a completely new .gnupg directory (and of >> course transferring keys and trust). >> >>> Trying to add "use-standard-socket" to $HOME/.gnupg/gpg-agent.conf >>> didn't make it (obsolete option...) >>> >>> Any idea ? >> Try to remove everything in gpg.conf and gpg-agent.conf except all >> entries which are absolutely necessary. >> >> Ludwig >> >> >> >> >> ___ >> 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 >> > ___ > 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 > ___ 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
Re: [Enigmail] Have to killall and relaunch gpg-agent after every reboot..
I found gpg-agent (gpg and gpg2 also) to be install in both /usr/bin & /usr/local/bin directories /usr/bin -rwxr-xr-x 1 root root 195 Oct 16 2012 fix_gpg_badsig -rwxr-xr-x 1 root root 1008632 Aug 18 13:54 gpg -rwxr-xr-x 1 root root 917032 Apr 8 12:14 gpg2 -rwxr-xr-x 1 root root 352872 Apr 8 12:14 gpg-agent -rwxr-xr-x 1 root root 139720 Apr 8 12:14 gpgconf -rwxr-xr-x 1 root root 142056 Apr 8 12:14 gpg-connect-agent -rwxr-xr-x 1 root root 26952 Feb 18 2016 gpg-error -rwxr-xr-x 1 root root2206 Feb 18 2016 gpg-error-config -rwxr-xr-x 1 root root 26696 Apr 8 12:14 gpgparsemail -rwxr-xr-x 1 root root 60296 Aug 18 13:54 gpgsplit -rwxr-xr-x 1 root root 372488 Aug 18 13:54 gpgv -rwxr-xr-x 1 root root3303 Aug 18 13:54 gpg-zip /usr/local/bin -rwxr-xr-x 1 root root 4385984 Aug 31 14:42 gpg2 -rwxr-xr-x 1 root root 1702688 Aug 31 14:42 gpg-agent -rwxr-xr-x 1 root root 499216 Aug 31 14:42 gpgconf -rwxr-xr-x 1 root root 655520 Aug 31 14:42 gpg-connect-agent -rwxr-xr-x 1 root root69856 Aug 31 14:39 gpg-error -rwxr-xr-x 1 root root 2201 Aug 31 14:39 gpg-error-config -rwxr-xr-x 1 zyx zyx114944 Feb 11 2015 gpgkey2ssh -rwxr-xr-x 1 root root 4493 Jun 15 21:34 gpgme-config -rwxr-xr-x 1 root root 209320 Jun 15 21:34 gpgme-tool -rwxr-xr-x 1 root root85864 Aug 31 14:42 gpgparsemail -rwxr-xr-x 1 root root 689144 Aug 31 14:42 gpgscm -rwxr-xr-x 1 root root 2193016 Aug 31 14:42 gpgsm -rwxr-xr-x 1 zyx zyx 4635 Feb 11 2015 gpgsm-gencert.sh -rwxr-xr-x 1 root root 641304 Aug 31 14:42 gpgtar -rwxr-xr-x 1 root root 2047760 Aug 31 14:42 gpgv2 Enigmail using /usr/local/bin/gpg2 instance Can I get rid of one of the two instances without any damage ? The oldest one I guess, the one in /usr/bin ? Le 01. 09. 16 à 22:28, Bitcoin Admin a écrit : > Yes, that 'other user' was me. And a fresh gnupg install solved the > dilemma, just imported the keyring and trustdb > > I had to remove one other file pubring.kbx, as it conflicts with the > pubring.gpg > Give it a try.. and report back > > Thomas > > On 09/01/2016 10:08 PM, acubene+enigm...@vivaldi.net wrote: >> OK thanks Ludwig >> I'll try that >> >> Le 01. 09. 16 à 22:06, Ludwig Hügelschäfer a écrit : >>> On 01.09.16 21:25, acubene+enigm...@vivaldi.net wrote: >>> (...) If I simply relaunch gpg-agent (without "--debug-level expert --use-standard-socket --daemon /bin/sh") Enigmail still doesn't work. >>> Some days another user had the same problem on Ubuntu 16.04. He solved >>> it by starting over with a completely new .gnupg directory (and of >>> course transferring keys and trust). >>> Trying to add "use-standard-socket" to $HOME/.gnupg/gpg-agent.conf didn't make it (obsolete option...) Any idea ? >>> Try to remove everything in gpg.conf and gpg-agent.conf except all >>> entries which are absolutely necessary. >>> >>> Ludwig >>> >>> >>> >>> >>> ___ >>> 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 >>> >> ___ >> 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 >> > > > ___ > 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 > ___ 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
Re: [Enigmail] Have to killall and relaunch gpg-agent after every reboot..
On Thu 2016-09-01 16:28:44 -0400, Bitcoin Admin wrote: > Yes, that 'other user' was me. And a fresh gnupg install solved the > dilemma, just imported the keyring and trustdb if you could send me a diff between your old gpg.conf and gpg-agent.conf (the ones that don't work) and the new ones (that do work), i'd be interested in seeing it. If there's sensitive info in it, feel free to redact. > I had to remove one other file pubring.kbx, as it conflicts with the > pubring.gpg If you're using the modern branch of gnupg, you're better off moving pubring.gpg out of the way and relying solely on pubring.kbx, rather than the other way around. You might try: mv ~/.gnupg/pubring.gpg ~/.gnupg/pubring.gpg.old gpg --import-options import-local --import < ~/.gnupg/pubring.gpg.old on debian systems where gpg is version 2.1 or higher, you might also try "migrate-pubring-from-classic-gpg". Regards, --dkg ___ 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
