Re: gnupg and pgp incompatibility
On Mon, Jul 24, 2000 at 02:27:49PM -0600, Charles Curley wrote: I use: set pgp_create_traditional=ask-no in my .muttrc. When i have a message to a correspondent who uses Eudora 3.x and an old pgp (3.6, I think), I hit "y", otherwise return. I suppose I should automate that with a send-hook. Real Soon Now. Note: that combination can handle signed or encrypted, but not both signed and encrypted. Charles, Thank you, David T-G and David C for your help. I'll talk to my correspondent about your solution and having to possibly chase the text. Then we'll maybe venture into macros. Or, hopefully, I can persuade him to load linux. I wish. Regards. -- Dennis Robertson 2/2 Sylvia Street NOOSAVILLE QLD 4566 Phone: 61 7 54742343 Mob: 0419 535539
Re: gnupg and pgp incompatibility
Charles, et al -- ...and then Charles Curley said... % On Mon, Jul 24, 2000 at 03:11:51PM -0400, David T-G muttered: % ...and then David Champion said... % % % % (Actually there are ways to make Mutt send messages that Eudora can % % handle, but these are kludgy and don't involve proper MIME. I think % % they involve macros. Again, check the web or archives.) ... % I searched both mutt archives and a teeny bit of the web in general, but % didn't find anything. Is "the old way" what you meant, or do you hint at % something else? % % I use: % % set pgp_create_traditional=ask-no Hokay; got that for sending to him, and he has to chase down the text. % % % in my .muttrc. When i have a message to a correspondent who uses Eudora % 3.x and an old pgp (3.6, I think), I hit "y", otherwise return. I suppose % I should automate that with a send-hook. Real Soon Now. send-hook . set pgp_autosign nopgp_autoencrypt pgp_create_traditional=no send-hook davidtg set pgp_autoencrypt send-hook eudora set nopgp_autosign pgp_create_traditional=yes Happy to help ;-) % % Note: that combination can handle signed or encrypted, but not both signed % and encrypted. Now, this is *very* interesting, since I sign everything including what I encrypt to him. I've sent him new-way and old-way encrypted-only test messages; let's see if they work for him *without* chasing... Is that the idea? % % -- % % -- C^2 % % No windows were crashed in the making of this email. % % Looking for fine software and/or web pages? % http://w3.trib.com/~ccurley :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: gnupg and pgp incompatibility
David, et al -- ...and then David Champion said... % On 2000.07.24, in [EMAIL PROTECTED], % "David T-G" [EMAIL PROTECTED] wrote: % David, et al -- % % % So, short answer: Eudora can send to Mutt, but Mutt can't send to % % Eudora, and it's Eudora's fault. % % FWIW, I have been able to send with mutt-0.95.4i and pgp5; my recipient % may whine a bit, but he's been reading the messages well for quite a % while now (since his upgrade a few months ago). % % Yes... to be more precise: Eudora can read signed messages, but (in my % experience) it can neither verify signed PGP/MIME messages, nor decrypt % encrypted PGP/MIME messages. Perhaps I should clarify: I've sent PGP/MIME signed+encrypted messages with mutt-0.95.4i and pgp5 (at least, I think I have been; didn't 0.95.4i do PGP/MIME unless you hacked up your own gawdawful macro as you quoted back to me?) and my pal reads them with no trouble (or, perhaps, following his typical procedure that is now comfortable for him, but I doubt it because he quotes my messages in replies and so I think it's Eudora doing the decoding and including). My big surprise was that there was apparently a change; mutt-0.95.4i+pgp5 worked fine, and mutt-1.2.4i+gpg-1.0.1 didn't, and I was signing and encrypting both times. I realize, of course, that I have changed two variables in this equation :-) % % In addition, I never have a problem reading his mail, but that could be % because I'm using the procmail recipe from PGP-Notes and don't have to % worry about it any more :-) % % Yeah. I just took that out of my own config so I can test this a % little more -- I've just been studying Eudora the last couple of days. Woo hoo -- and, believe me, I wish you luck and great success! % % ME gave some sample macros for circumventing this issue when he posted % his edit-type patch, I think; these should work in absence of % procmail. How nice. Of course, I plan to stick with procmail :-) % % I tried sending old-style messages with pgp_create_traditional; he tells % me that Eudora detaches the message and he has to go and find it and % open it (he chooses to use Word, of all things!), and the text is there. % % I'm not familiar with pgp_create_traditional -- I haven't been paying % attention to this area of development, since it all works OK for me so % far. :) Just in case you're *really* not familiar, it's a variable that lets you call your pgp_clearsign_command (a variable holding that command structure) instead of pgp_sign_command (the command to do PGP/MIME signing). I know you can RTFM, so I'll only point you to 6.3.115 and 6.3.120/6.3.121 :-) Interestingly enough, as I review my gpg.rc to get the exact names of these variables I see that there is a clearsign command but not, apparently, an equivalent clearencrypt or inlineencrypt command. I just checked the encrypted-only old-style test message I sent a few minutes ago, and it *did* look right, but maybe I don't know for what I'm looking... % % I searched both mutt archives and a teeny bit of the web in general, but % didn't find anything. Is "the old way" what you meant, or do you hint at % something else? % % Yes: I was referring to macros for filtering components through % PGP/GPG. You posted one of them. (Ah, no substitute for personal Aha! Yes, I still have those in my muttrc :-) I was specifically searching against "Eudora", so it makes sense that my post wouldn't have come up. % archives. Web archives can all * * *!) Yeah. Pretty much. And I even meant to do something about that and haven't gone forward with it. Oh, well. % % Here are examples with citations, altered a bit to be more readable. A % lot of you have these already, but maybe this makes a useful summary % for the FAQ or something. I think these will work, but I haven't Very cool! Thanks! % tested them all since rewriting them. Check primary sources if in % doubt. Always a good idea. % % I'm not sure which of these would work best with Eudora, and my % "Eudora-empowered" PC is not at hand. Dare I hope that you'll be poking at this some more one day soon? % % The usual disclaimers: I don't mean to suggest that there aren't better % sources for this stuff; this is just what I found. No resposibility if % this stuff crashes your mailer, erases your mail, drowns your fish, % etc. Everything I say is a lie. *grin* Thanks again! :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: gnupg and pgp incompatibility
David, et al -- ...and then David Champion said... % On 2000.07.22, in [EMAIL PROTECTED], % "Dennis Robertson" [EMAIL PROTECTED] wrote: % Hello List, % I am trying to correspond with a friend who uses Windows and Eudora 4.3.2 (gasp!) with PGP Hey, same here. Oh, darn. ... % 4.3.2 will issue valid PGP/MIME, which mutt can read, but it can not % read PGP/MIME issued by either mutt or itself. (Yes: Eudora cannot % read its own output.) Oy. % % So, short answer: Eudora can send to Mutt, but Mutt can't send to % Eudora, and it's Eudora's fault. FWIW, I have been able to send with mutt-0.95.4i and pgp5; my recipient may whine a bit, but he's been reading the messages well for quite a while now (since his upgrade a few months ago). In addition, I never have a problem reading his mail, but that could be because I'm using the procmail recipe from PGP-Notes and don't have to worry about it any more :-) % % (Actually there are ways to make Mutt send messages that Eudora can % handle, but these are kludgy and don't involve proper MIME. I think % they involve macros. Again, check the web or archives.) I tried sending old-style messages with pgp_create_traditional; he tells me that Eudora detaches the message and he has to go and find it and open it (he chooses to use Word, of all things!), and the text is there. I searched both mutt archives and a teeny bit of the web in general, but didn't find anything. Is "the old way" what you meant, or do you hint at something else? % % -- % -D. [EMAIL PROTECTED]NSITUniversity of Chicago TIA HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: gnupg and pgp incompatibility
On Mon, Jul 24, 2000 at 03:11:51PM -0400, David T-G muttered: David, et al -- ...and then David Champion said... % On 2000.07.22, in [EMAIL PROTECTED], % "Dennis Robertson" [EMAIL PROTECTED] wrote: % Hello List, % I am trying to correspond with a friend who uses Windows and Eudora 4.3.2 (gasp!) with PGP Hey, same here. Oh, darn. ... % 4.3.2 will issue valid PGP/MIME, which mutt can read, but it can not % read PGP/MIME issued by either mutt or itself. (Yes: Eudora cannot % read its own output.) Oy. % % So, short answer: Eudora can send to Mutt, but Mutt can't send to % Eudora, and it's Eudora's fault. FWIW, I have been able to send with mutt-0.95.4i and pgp5; my recipient may whine a bit, but he's been reading the messages well for quite a while now (since his upgrade a few months ago). In addition, I never have a problem reading his mail, but that could be because I'm using the procmail recipe from PGP-Notes and don't have to worry about it any more :-) % % (Actually there are ways to make Mutt send messages that Eudora can % handle, but these are kludgy and don't involve proper MIME. I think % they involve macros. Again, check the web or archives.) I tried sending old-style messages with pgp_create_traditional; he tells me that Eudora detaches the message and he has to go and find it and open it (he chooses to use Word, of all things!), and the text is there. I searched both mutt archives and a teeny bit of the web in general, but didn't find anything. Is "the old way" what you meant, or do you hint at something else? I use: set pgp_create_traditional=ask-no in my .muttrc. When i have a message to a correspondent who uses Eudora 3.x and an old pgp (3.6, I think), I hit "y", otherwise return. I suppose I should automate that with a send-hook. Real Soon Now. Note: that combination can handle signed or encrypted, but not both signed and encrypted. -- -- C^2 No windows were crashed in the making of this email. Looking for fine software and/or web pages? http://w3.trib.com/~ccurley PGP signature
Re: gnupg and pgp incompatibility
On 2000.07.24, in [EMAIL PROTECTED], "David T-G" [EMAIL PROTECTED] wrote: David, et al -- % So, short answer: Eudora can send to Mutt, but Mutt can't send to % Eudora, and it's Eudora's fault. FWIW, I have been able to send with mutt-0.95.4i and pgp5; my recipient may whine a bit, but he's been reading the messages well for quite a while now (since his upgrade a few months ago). Yes... to be more precise: Eudora can read signed messages, but (in my experience) it can neither verify signed PGP/MIME messages, nor decrypt encrypted PGP/MIME messages. In addition, I never have a problem reading his mail, but that could be because I'm using the procmail recipe from PGP-Notes and don't have to worry about it any more :-) Yeah. I just took that out of my own config so I can test this a little more -- I've just been studying Eudora the last couple of days. ME gave some sample macros for circumventing this issue when he posted his edit-type patch, I think; these should work in absence of procmail. I tried sending old-style messages with pgp_create_traditional; he tells me that Eudora detaches the message and he has to go and find it and open it (he chooses to use Word, of all things!), and the text is there. I'm not familiar with pgp_create_traditional -- I haven't been paying attention to this area of development, since it all works OK for me so far. :) I searched both mutt archives and a teeny bit of the web in general, but didn't find anything. Is "the old way" what you meant, or do you hint at something else? Yes: I was referring to macros for filtering components through PGP/GPG. You posted one of them. (Ah, no substitute for personal archives. Web archives can all * * *!) Here are examples with citations, altered a bit to be more readable. A lot of you have these already, but maybe this makes a useful summary for the FAQ or something. I think these will work, but I haven't tested them all since rewriting them. Check primary sources if in doubt. I'm not sure which of these would work best with Eudora, and my "Eudora-empowered" PC is not at hand. The usual disclaimers: I don't mean to suggest that there aren't better sources for this stuff; this is just what I found. No resposibility if this stuff crashes your mailer, erases your mail, drowns your fish, etc. Everything I say is a lie. + Basic composition filter to traditionally encode the current message component (typically the only component in a us-ascii, text/plain message), using PGP 2 or NAI's PGP 6. [1] macro compose S "filter-entrypgp +verbose=0 -fast \ +clearsig=on\nyedit-typekill-lineapplication/pgp; \ format=text; x-action=sign\n" + Use of the edit-type function to coerce a message into application/pgp format without use of procmail. [2] macro index \eS "edit-typekill-lineapplication/pgp; format=text; \ x-action=sign\n" macro index \eE "edit-typekill-lineapplication/pgp; format=text; \ x-action=encrypt\n" macro pager \eS "edit-typekill-lineapplication/pgp; format=text; \ x-action=sign\n" macro pager \eE "edit-typekill-lineapplication/pgp; format=text; \ x-action=encrypt\n" macro attach \eS "edit-typekill-lineapplication/pgp; format=text; \ x-action=sign\n" macro attach \eE "edit-typekill-lineapplication/pgp; format=text; \ x-action=encrypt\n" + Composition filters for signing and encryption with PGP 5. [3] # old-style signing macro compose S "filter-entrypgps +verbose=0 -fat \ +clearsig=on\nyedit-typekill-lineapplication/pgp;format=text; \ x-action=sign\n" # old-style encrypting ### have to hard-code recipient for now... macro compose E "filter-entrypgpe -s -r RECIPIENT -r 0xYOURKEY \ -fat\nyapplication/pgp; format=text; x-action=encrypt\n" D. T-G: "There is a patch out there, I believe, which will let you insert %r at RECIPIENT, but I forget what it is :-)" dgc: I'm not sure how this applies, myself, since there's no context in which to select a recipient. Seems you'd need pgpe to ask you, but I've never used it, so I'll leave it alone. + Composition filter for application/pgp signing using GnuPG. [4] macro compose S "filter-entrygpg --sign --armor --textmode \ --clearsign\nyedit-typekill-lineapplication/pgp; format=text; \ x-action=sign\n" 'clearsign the message' + Composition filter for very traditional (not even MIME at all) signing and encrypting, using PGP 2 or PGP 6. [5] macro compose S "filter-entrypgp +verbose=0 -fast +clearsig=on\nyedit-typekill-linetext/plain\n" macro compose E "filter-entrypgp +verbose=0 -feast +clearsig=on\nyedit-typekill-linetext/plain\n" [1] Included documentation, from mutt-*.*.*/doc/PGP-Notes.txt [2] M. Elkins, in [EMAIL PROTECTED] [3] D. T-G, in [EMAIL PROTECTED] [4] [EMAIL PROTECTED], in m12rJjB-000jXxC@localhost [5] C. Cera, in [EMAIL PROTECTED] -- -D.
gnupg and pgp incompatibility
Hello List, I am trying to correspond with a friend who uses Windows and Eudora 4.3.2 (gasp!) with PGP 6.5.3. I use mutt and gnupg 1.0.1 ;). When he invokes decrypt on my messages all he sees is: "Content-type: text/plain: charset=us-ascii". That is the end of the process; no text is visible. He has no difficulty corresponding with me and others using pgp and windows. I have read of mutt's alleged shortcomings with mime on the qmail list. Is there a way to make mutt/gnupg and windows/eudora/pgp 6.5.3 talk to each other? TIA. -- Dennis Robertson 2/2 Sylvia Street NOOSAVILLE QLD 4566 Phone: 61 7 54742343 Mob: 0419 535539
Re: gnupg and pgp incompatibility
On 2000.07.22, in [EMAIL PROTECTED], "Dennis Robertson" [EMAIL PROTECTED] wrote: Hello List, I am trying to correspond with a friend who uses Windows and Eudora 4.3.2 (gasp!) with PGP 6.5.3. I use mutt and gnupg 1.0.1 ;). When he invokes decrypt on my messages all he sees is: "Content-type: text/plain: charset=us-ascii". That is the end of the process; no text Are you certain that you have mutt properly configured? What do you for a content-type if you bcc yourself one of these messages? What about Fcc:? is visible. He has no difficulty corresponding with me and others using pgp and windows. I have read of mutt's alleged shortcomings with mime on the qmail list. Is there a way to make mutt/gnupg and windows/eudora/pgp 6.5.3 talk to each other? I don't know about these allegations. As far as I know, mutt does PGP/MIME perfectly, but does not do SMIME or application/pgp. Eudora 4.3.2 will issue valid PGP/MIME, which mutt can read, but it can not read PGP/MIME issued by either mutt or itself. (Yes: Eudora cannot read its own output.) There are procmail rules for bending Eudora's usual PGP output into a format Mutt can work with. Check the web site or list archives. So, short answer: Eudora can send to Mutt, but Mutt can't send to Eudora, and it's Eudora's fault. (Actually there are ways to make Mutt send messages that Eudora can handle, but these are kludgy and don't involve proper MIME. I think they involve macros. Again, check the web or archives.) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
