Re: Problems with Gnus (Emacs) + GnuPG for signing a mail with S/MIME
Am Freitag 11 November 2022 14:40:13 schrieb Angel de Vicente: > I actually have no problems signing with S/MIME also inside Emacs (as > far as the passphrase has been cached). And I have no problems signing > with PGP (pinentry loopback works fine then). > > So it looks like something that affects exclusively pinentry loopback > while signing with S/MIME As always, there must be a difference in how OpenPGP and S/MIME signing with GnuPG is called from Emacs/Gnus. (There is a small chance that it is with the specific keypair you are using.) Comparing detailed logs of OpenPGP and S/MIME might reveal the difference. I darkly remember Gnus using GPGME, if this is the case, maybe a GPGME_DEBUG log can help you. Otherwise you need to look into how Emacs can produce more details about what it is going (I am not an Emacs user, so I cannot really help you there.) Regards Bernhard signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Problems with Gnus (Emacs) + GnuPG for signing a mail with S/MIME
Hello, Bernhard Reiter writes: > Am Freitag 04 November 2022 20:03:35 schrieb Angel de Vicente: >> Any ideas as to what might cause this? > > Not really, I would start the analysis by asserting that > gpgsm --sign > still works outside of Emacs and then somehow try to emulate the loopback > mode. Maybe there is a different problem somewhere. gpgsm --sign outside of Emacs does work without any problems. I actually have no problems signing with S/MIME also inside Emacs (as far as the passphrase has been cached). And I have no problems signing with PGP (pinentry loopback works fine then). So it looks like something that affects exclusively pinentry loopback while signing with S/MIME (actually you will see this e-mail signed with S/MIME. Basically I try to sign it, if I get the error because the passphrase was not cached, I simply sign a region with PGP (which asks me correctly for the passphrase and it gets cached, and then I have no problem signing and sending the message). I really have no clue what could be going on... Thanks, -- Ángel de Vicente Research Software Engineer (Supercomputing and BigData) Tel.: +34 922-605-747 Web.: http://research.iac.es/proyecto/polmag/ GPG: 0x8BDC390B69033F52 smime.p7s Description: S/MIME cryptographic signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Difference between versions--Question
On Freitag, 11. November 2022 14:06:34 CET Bernhard Reiter wrote: > Am Freitag 04 November 2022 13:55:58 schrieb K S via Gnupg-users: > > How do I run configure to get the compression routines? > > checkout the "config.log" or the output of your configure command run > to see if there are messages concerning compression libraries. It depends on your distribution what packages you need to install to get support for compression. Typically, those packages would be called something like zlib-devel, zip-devel, bzip2-devel, or similar. configure will very likely have told you that it didn't find zlib, zip and bzip2. Just running configure without looking at its output will allow you to build an application, but you may miss optional feature like, in the case of gnupg, support for different types of compression. Regards, Ingo signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Troubleshooting help
On Fri, 11 Nov 2022 10:58, Andrea Lenarduzzi said: > Thank you > gpg-connect-agent 'scd getinfo reader_list' /byeD > 058F:9540:X:0%0A076B:3031:X:0%0AOK Unencoding the above list: 058F:9540:X:0 076B:3031:X:0 Thus you have two reader and you need to either use --8<---cut here---start->8--- reader-port 058F:9540:X:0 --8<---cut here---end--->8--- or --8<---cut here---start->8--- reader-port 076B:3031:X:0 --8<---cut here---end--->8--- into your ~/.gnupg/scdameon.con and restart the daemon (gpgconf --kill all) Shalom-Salam, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein openpgp-digital-signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Difference between versions--Question
Hi Kevin, Am Freitag 04 November 2022 13:55:58 schrieb K S via Gnupg-users: > How do I run configure to get the compression routines? checkout the "config.log" or the output of your configure command run to see if there are messages concerning compression libraries. > FYI, this is the first time I've built from source. It is cool that you have tried it! :) Bernhard -- https://intevation.de/~bernhard +49 541 33 508 3-3 Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Problems with Gnus (Emacs) + GnuPG for signing a mail with S/MIME
Am Freitag 04 November 2022 20:03:35 schrieb Angel de Vicente: > Any ideas as to what might cause this? Not really, I would start the analysis by asserting that gpgsm --sign still works outside of Emacs and then somehow try to emulate the loopback mode. Maybe there is a different problem somewhere. Bernhard -- https://intevation.de/~bernhard +49 541 33 508 3-3 Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Troubleshooting help
Am Freitag 11 November 2022 11:58:42 schrieb Andrea Lenarduzzi via Gnupg-users: > gpg: selecting card failed: with #reader-port 32768 and disable-ccid-driver You probably know that -v (several times) and --debug-all on many GnuPG binaries can greatly increase the verbosity and thus help to see more. Bernhard -- https://intevation.de/~bernhard +49 541 33 508 3-3 Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Troubleshooting help
Thank you gpg-connect-agent 'scd getinfo reader_list' /byeD 058F:9540:X:0%0A076B:3031:X:0%0AOK but gpg --card-edit gpg: selecting card failed: with #reader-port 32768 and disable-ccid-driver Il venerdì 11 novembre 2022 alle ore 08:38:08 CET, Werner Koch ha scritto: On Thu, 10 Nov 2022 11:57, Andrea Lenarduzzi said: > disabled-ccid-driver I hope that is a c=P error. The option is called "disable-ccid-driver" and not "disabled-..." > reader-port 32768 That is a very unlikley reader port sepcification you need to use the strings as shown by PC/SC. If you run 2.2 gpg-connect-agent 'scd getinfo reader_list' /bye may give you a list of available reader. > gpg: selecting card failed Likely with the above reader port. Shalom-Salam, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
