Re: no passphrase request
On Sun 2016-05-29 14:29:02 -0400, Bob Holtzman wrote: > Running Debian Jessie with mutt 1.5.23 and gnupg 1.4.18-7 (yeah, I know > it's old, but then so am I) > > Trying to send an test message to myself using mutts' compiled-in gpg > support. After selecting an action from the menu, (sign encrypt, etc) and > hitting return, I'm prompted for a key ID, never for a passphrase. The > message then refuses to send. > > In checking for mutts' compiled options, I ran across this which may > have some bearing on what I'm seeing, or not. The options in question > are: +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME > +CRYPT_BACKEND_GPGME. I'm assuming if it handles classic pgp it will > also handle gnupg. Yes? > > Searches and doc reading haven't turned up much of anything. > > Any pointers on how to get out of this appreciated. This sounds like a Mutt issue more than a GnuPG issue. You might try the Mutt mailing lists or the Mutt wiki: http://www.mutt.org/mail-lists.html https://dev.mutt.org/trac/wiki/MuttWiki hth, --dkg signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Fw: GnuPG - Encryption process issues.
Hi Carlos-- Please reply in the original thread, to make it easier for people to follow the discussion. I've added some References: headers back in here so some mailers might merge the threads, but this won't work for everyone. Also, when sharing terminal transcripts, sending mail without unnecessary line-wrapping will make them much easier for your readers to interpret. It looks like you're trying to sign the file (that's what the "-s" part of "-se" means). For whatever reason, the signature itself is likely to be what is failing, and not the encryption. If you drop the signatures in your test (using -e instead of -se) do they all complete cleanly? To be clear: I'm not saying you shouldn't sign at the same time as encrypting, i'm trying to help you narrow down the cause of the problem. I also see you fiddling with the ownership of ~/.gnupg/random_seed -- you really shouldn't need to do that, and ideally each user will control their own random_seed automatically -- you shouldn't be sharing a gnupg home directory between to different user accounts unless you absolutely need to. --dkg signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Fw: GnuPG - Encryption process issues.
Dear Daniel Kahn Gillmor, Please find the information/evidence requested below provided by our Unix Team Specialist, it is very important for us your input since it will help to find the specific Root Cause. If you require additional details, please do not hesitate to ask. Thanks in advance. @ Thanks Ankit for your detailed response. Carlos A. Moreno Torres Problem Management | CEMEX Global Technology Services | IBM Corporation Office: (+52-81) 8328-5251 IBM E-mail: cmore...@mx1.ibm.comAv. Constitución No. 444 Pte. IBM @ CEMEX Collaboration HUB: ibm.biz/Bdx93b Monterrey, NL 64000 México From: Ankit Bhardwaj5/India/IBM To: Carlos Alberto Moreno Torres/Mexico/Contr/IBM@IBMMX Cc: Ajay B Challa/India/IBM@IBMIN, Ivan Fernando Montes de Oca Tavera/Mexico/Contr/IBM@IBMMX, "Juan Carlos Garcia" , Samuel Ramos Javier/Mexico/IBM@IBMMX, "Samuel Mizrain Ramos Javier" , Srinivas Masetty/India/IBM@IBMIN Date: 05/31/2016 10:46 AM Subject:Re: Fw: GnuPG - Encryption process issues. Hello Carlos Please share below information with GPG team i think by seeing the results of test performed by us on system they will able to give us the solution We have tested below things in envirnoment -> Userd Details used in this test root ehpadm Permissions under user "root" -> Directory Permission of root drwx--2 root sapsys 4096 May 31 09:39 /home/root/.gnupg -> Files Under /home/root/.gnupg -rw---1 root sapsys 1280 Sep 13 2011 trustdb.gpg -rw---1 root sapsys 4805 Sep 13 2011 secring.gpg -r1 root sapsys 9088 Sep 13 2011 gpg.conf -rw---1 root sapsys 7438 May 21 2013 pubring.gpg~ -rw---1 root sapsys 8557 Nov 8 2013 pubring.gpg -rw---1 root sapsys 11 Apr 28 08:44 .#lk200104a8.mxoccsapehpn2.8716480 -rw---1 root sapsys 11 Apr 28 08:53 .#lk2000c2c8.mxoccsapehpn2.11141460 -rw---1 root sapsys 11 Apr 28 12:00 .#lk200104b8.mxoccsapehpn2.8978598 -rw---1 root sapsys 11 Apr 29 08:57 .#lk2000c2c8.mxoccsapehpn2.12911042 -rw---1 root sapsys 11 May 2 11:32 .#lk200104b8.mxoccsapehpn2.10748294 -rw---1 root sapsys 11 May 2 19:34 .#lk200104b8.mxoccsapehpn2.7471568 -rw---1 root sapsys 11 May 2 22:23 .#lk2000c328.mxoccsapehpn2.12058746 -rw---1 root sapsys 11 May 2 23:46 .#lk200104b8.mxoccsapehpn2.6750230 -rw---1 root sapsys 11 May 3 10:28 .#lk200104b8.mxoccsapehpn2.14221392 -rw---1 root sapsys 11 May 3 13:45 .#lk200104b8.mxoccsapehpn2.9240874 -rw---1 root sapsys 600 May 31 09:39 random_seed ->Permissions under user "ehpadm" drwx--2 ehpadm sapsys 4096 May 31 09:48 /home/ehpadm/.gnupg -> Files Under /home/ehpadm/.gnupg -rw---1 ehpadm sapsys 1200 May 3 21:54 trustdb.gpg -rw---1 ehpadm sapsys 7438 May 3 21:54 pubring.gpg~ -rw---1 ehpadm sapsys 8557 May 3 21:54 pubring.gpg -rw---1 ehpadm sapsys 4805 May 3 21:54 secring.gpg -rw---1 ehpadm sapsys 11 May 3 22:03 .#lk200104b8.mxoccsapehpn2.6488076 -rw---1 ehpadm sapsys 9029 May 4 11:18 gpg.conf -rw---1 ehpadm sapsys 11 May 4 13:43 .#lk2000c328.mxoccsapehpn2.6160766 -rw---1 ehpadm sapsys 11 May 4 13:55 .#lk2000c328.mxoccsapehpn2.8913004 -rw---1 ehpadm sapsys 11 May 4 15:55 .#lk2000c328.mxoccsapehpn2.12976528 -rw---1 ehpadm sapsys 11 May 4 17:58 .#lk2000c328.mxoccsapehpn2.10158578 -rw---1 ehpadm sapsys 11 May 4 18:06 .#lk2000c328.mxoccsapehpn2.5308674 -rw---1 ehpadm sapsys0 May 31 10:00 random_seed Test 1 # ---Failed Test ->Created file name "testehpadm" in ehpadm home directory -rw-r--r--1 ehpadm sapsys6 May 31 10:06 /home/ehpadm/testehpadm -> Invoke GPG progrma using below command /opt/freeware/gnupg/bin/gpg
