GnuPG signing glitch
I'm having some trouble GPG-signing my outgoing messages. For example if I __'s'ign__ from the PGP options menu, these headers appear (these appear to be the defaults right now): sign as: Russell HooverMIC algorithm: pgp-sha1 I then hit RETURN, enter my passphrase, and I get: gpg: Segmentation fault caught ... exiting Press any key to continue... but if I __sign 'a's__ from the PGP options menu, and hit RETURN at the "sign as:" prompt at the bottom of the screen (and then select my name key id from the list presented) it puts these headers in: sign as: 0xFC5C7370MIC algorithm: pgp-rmd160 This time when I hit RETURN and enter my passphrase, the mail is sent, **signed**, with no problems. Any suggestions? -- // [EMAIL PROTECTED] // PGP signature
Re: Some changes / additions to the mutt-newbie docs (mutt-newbie.sourceforge.net)
On Mon 10/02/00 at 06:50 PM +0530, Suresh Ramasubramanian [EMAIL PROTECTED] wrote: [-- Type: text/sgml, Encoding: 7bit, Size: 10K --] What is a preferable mailcap entry for text/sgml? I have: text/sgml; lynx -dump %s; needsterminal; copiousoutput but this produces one long monolithic block of text with no line-spaces, tabs, paragraph indents, etc. Is this the best that can be done? -- // [EMAIL PROTECTED] //
Re: GnuPG signing glitch
Russell Hoover [[EMAIL PROTECTED]] wrote: I'm having some trouble GPG-signing my outgoing messages. For example if I __'s'ign__ from the PGP options menu, these headers appear (these appear to be the defaults right now): sign as: Russell HooverMIC algorithm: pgp-sha1 I then hit RETURN, enter my passphrase, and I get: gpg: Segmentation fault caught ... exiting Press any key to continue... but if I __sign 'a's__ from the PGP options menu, and hit RETURN at the "sign as:" prompt at the bottom of the screen (and then select my name key id from the list presented) it puts these headers in: sign as: 0xFC5C7370MIC algorithm: pgp-rmd160 This time when I hit RETURN and enter my passphrase, the mail is sent, **signed**, with no problems. Any suggestions? What do you have set for $pgp_sign_as? This should be a key id (0xFC5C7370), not your name (Russell Hoover). I've no idea if this is it, but it's the first thing that comes to mind. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- the crises posed a question / just beneath the skin the virtue in my veins replied / that quitters never win PGP signature
Re: GnuPG signing glitch
On Mon 10/02/00 at 04:28 PM -0500, Jeremy Blosser [EMAIL PROTECTED] wrote: What do you have set for $pgp_sign_as? This should be a key id (0xFC5C7370), not your name (Russell Hoover). That's it -- it *was* set to my name. Why did I think it should be? Was this the case at some time in the past? I must have read that to have set it that way. Or maybe not, who know. Anyway I've now set it to my public key id and that fixed the problem. I should have picked up on this myself when I said that seemed to be the default -- I just couldn't remember exactly where it was set. **thanks** -- // [EMAIL PROTECTED] //
mutt/sendmail mailing list problem
hi kids... on one of the mailing lists i'm subscribed to, none of my messages get through. the problem is that i'm subscribed as [EMAIL PROTECTED], but mutt sendmail set my Return-Path to [EMAIL PROTECTED], which doesn't even exist (mugwort is my local username on the freebsd box; dnai is my isp). their maillist software requires that the return-path be the same as my subscription address. i have in .muttrc these relevant lines: set envelope_from=yes set [EMAIL PROTECTED] i've also tried: my_hdr From: [EMAIL PROTECTED] set sendmail='/usr/sbin/sendmail [EMAIL PROTECTED] -oem -oi' my_hdr Return-Path: [EMAIL PROTECTED] is there any way to do this, or am i doomed to actually go to yahoo to use this mailing list?? thanks peter -- Peter Jaques [EMAIL PROTECTED] http://cs.oberlin.edu/~pjaques klezmerbalkanturkish clarinet; free foodshelter; books to prisoners PGP signature
