pgpenvelope-users Mailing List for pgpenvelope (Page 6)
Brought to you by:
ftobin
Menu
▾
▴
pgpenvelope-users — general pgpenvelope users discussion
You can subscribe to this list here.
| 2000 |
Jan
(1) |
Feb
(22) |
Mar
(11) |
Apr
(9) |
May
(1) |
Jun
(9) |
Jul
(28) |
Aug
(9) |
Sep
(10) |
Oct
(26) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(8) |
Feb
(2) |
Mar
|
Apr
(2) |
May
(6) |
Jun
|
Jul
(4) |
Aug
(8) |
Sep
(9) |
Oct
|
Nov
(2) |
Dec
(8) |
| 2002 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(2) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: John A. P. <pe...@jp...> - 2000-07-15 00:39:14
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 14 Jul 2000, Frank Tobin wrote: > -----BEGIN PGPENVELOPE PROCESSED MESSAGE----- > > Frank Tobin, at 14:13 -0500 on Fri, 14 Jul 2000, wrote: > > > L. Sassaman, at 11:57 -0700 on Fri, 14 Jul 2000, wrote: > > > > > That is the error: "gnupg produced no output". Too late now but I was going to report that 2.8.9 was working fine on my system. What was the problem? - -- John Perry pe...@jp... PGP-encrypted e-mail welcome! PGP/GPG key 164BDBAE ICQ# 64823745 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: pgpenvelope 2.8.8 - http://pgpenvelope.sourceforge.net/ iD8DBQE5b7Kr7YSEAxZL264RArr0AKDX2j86Ik3v4sG0Jv2zOcol2eBRTQCfSLix D0616OG8GSpj145jcO6DG/0= =RnhP -----END PGP SIGNATURE----- |
|
From: L. S. <ra...@qu...> - 2000-07-14 21:09:28
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 14 Jul 2000, Frank Tobin wrote: > The just-released 2.8.10 addresses and fixes this bug. If only all software development had a turn-around time like that for bug fixes. __ L. Sassaman System Administrator | "Every window on Alcatraz has Technology Consultant | a view of San Francisco." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Susanna Kaysen -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5b4GEPYrxsgmsCmoRAsYpAJ46HskQG5V8xi++CbNEYcHxaABp6wCg4EoI eDPooOkkDZ7QQ7R3SiKGWWY= =76De -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-07-14 20:03:26
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Frank Tobin, at 14:13 -0500 on Fri, 14 Jul 2000, wrote: > L. Sassaman, at 11:57 -0700 on Fri, 14 Jul 2000, wrote: > > > That is the error: "gnupg produced no output". > > I verify that it isn't working on your system. I'll look into this. The just-released 2.8.10 addresses and fixes this bug. - -- Frank Tobin http://www.uiuc.edu/~ftobin/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.2 (FreeBSD) Comment: pgpenvelope 2.8.10 - http://pgpenvelope.sourceforge.net/ iEYEARECAAYFAjlvcgsACgkQVv/RCiYMT6OSPwCfSqVse2mmZsn5vvUFbBo4z5Lh fKEAnjUK4ovqV0lhQ2pWRPJ8mBj+NupU =LEYY -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-07-14 19:13:57
|
L. Sassaman, at 11:57 -0700 on Fri, 14 Jul 2000, wrote: > That is the error: "gnupg produced no output". I verify that it isn't working on your system. I'll look into this. -- Frank Tobin http://www.uiuc.edu/~ftobin/ |
|
From: L. S. <ra...@qu...> - 2000-07-14 18:57:28
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 13 Jul 2000, Frank Tobin wrote: > -----BEGIN PGPENVELOPE PROCESSED MESSAGE----- > > L. Sassaman, at 10:24 -0700 on Thu, 13 Jul 2000, wrote: > > > Cannot decrypt email. "gnupg produced no output". > > Could you be more descriptive as to what error is happening? Are you That is the error: "gnupg produced no output". > receiving signed mails, or encrypted ones? Can you reproduce the I cannot decrypt or verify email. I think there is a bug in pgpenvelope_decrypt. I can sign/encrypt email just fine. > error? If you look at the mail 'rawly' in your Mailbox, does it look like > a 'correct' OpenPGP block? Yes. The problem is with the interaction of GnuPG and pgpenvelope. Note that the problem is not GnuPG::Interface, as I downgraded to pgpenvelope 2.8.8, but left the interface module at the new version. __ L. Sassaman System Administrator | "Every window on Alcatraz has Technology Consultant | a view of San Francisco." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Susanna Kaysen -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5b2KUPYrxsgmsCmoRAqVXAJ475iocudlZk+ZOaaqXiexNwbUUTwCeIGXy BX/FGS8IMSJnkqd6sIyt+rI= =gVhm -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-07-14 01:21:09
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a quick notice to the users of this list that the subject prefix that had previously been applied to this list won't be enabled anymore. The reason for the change is that most mailing lists don't use any such prefix anyways, and one can still filter messages based on other critera (such as the To: or CC: fields). - -- Frank Tobin http://www.uiuc.edu/~ftobin/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.2 (FreeBSD) Comment: pgpenvelope 2.8.9 - http://pgpenvelope.sourceforge.net/ iEYEARECAAYFAjluawEACgkQVv/RCiYMT6PFSACbBPv+Z+mdgRUPKgGMtoFPBLmV 63QAnRdGgbXaqbha0qZVCjGRLrV4tKuq =nB4A -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-07-13 22:27:28
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 L. Sassaman, at 10:24 -0700 on Thu, 13 Jul 2000, wrote: > Cannot decrypt email. "gnupg produced no output". Could you be more descriptive as to what error is happening? Are you receiving signed mails, or encrypted ones? Can you reproduce the error? If you look at the mail 'rawly' in your Mailbox, does it look like a 'correct' OpenPGP block? - -- Frank Tobin http://www.uiuc.edu/~ftobin/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.2 (FreeBSD) Comment: pgpenvelope 2.8.9 - http://pgpenvelope.sourceforge.net/ iEYEARECAAYFAjluQk4ACgkQVv/RCiYMT6N7SQCePaIzcD56Da8jxDD+kHqJ2cKi hs0An28GSywnwNLRLGUrA0MNUTIpge0B =iXVi -----END PGP SIGNATURE----- |
|
From: L. S. <ra...@qu...> - 2000-07-13 17:24:42
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cannot decrypt email. "gnupg produced no output". __ L. Sassaman System Administrator | Technology Consultant | "Credo quia absurdum." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Tertullian -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5bftVPYrxsgmsCmoRAjhfAKCw6Mkt5AYI7Pqxakz3t3F+wZvb0wCg6THP U3YWam+yF2jKLurXlIuZ2/8= =x6SU -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-06-26 19:44:07
|
L. Sassaman, at 12:12 -0700 on Mon, 26 Jun 2000, wrote: > 1-----BEGIN PGP MESSAGE----- Yeah, I forget to set that config variable as a string value instead of a boolean. Fixed in CVS. -- Frank Tobin http://www.uiuc.edu/~ftobin/ |
|
From: L. S. <ra...@qu...> - 2000-06-26 19:16:39
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 24 Jun 2000, Frank Tobin wrote: > L. Sassaman, at 15:14 -0700 on Sat, 24 Jun 2000, wrote: > > > Ah. So Pine just sucks. > > Tell me one piece of software that lets you do exactly you want for every > single instance :) Ahthough Pine shoudl be more configurable in this > respect. pgpenvelope, of course! =) > > One "#" might be prettier, and would have the same effect, no? > > Tis configurable. Or it appears to be, anyway. But no matter what you put in the config line for the prefix character, you end up getting this displayed when you opt out of decrypting: 1-----BEGIN PGP MESSAGE----- (It always uses a "1") __ L. Sassaman System Administrator | "Everything looks bad Technology Consultant | if you remember it." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Homer Simpson -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5V6sPPYrxsgmsCmoRAs4aAKDMyTvZbUpv4nV4fNT/+uBAFldUPwCgvK0b A2mg5lXZjlHFG/78tFUxrRE= =ggYi -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-06-24 22:23:30
|
L. Sassaman, at 15:14 -0700 on Sat, 24 Jun 2000, wrote: > Ah. So Pine just sucks. Tell me one piece of software that lets you do exactly you want for every single instance :) Ahthough Pine shoudl be more configurable in this respect. > One "#" might be prettier, and would have the same effect, no? Tis configurable. -- Frank Tobin http://www.uiuc.edu/~ftobin/ |
|
From: L. S. <ra...@qu...> - 2000-06-24 22:18:49
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 24 Jun 2000, Frank Tobin wrote: > -----BEGIN PGPENVELOPE PROCESSED MESSAGE----- > > L. Sassaman, at 00:54 -0700 on Sat, 24 Jun 2000, wrote: > > > Can we have pgpenvelope behave such that when a user selects no to not > > decrypt, the message that has been passed to the filter is passed back, > > totally unchanged? That would be perfect. > > I can't leave it 'totally' unchanged, for two reasons. If > pgpenvelope_decrypt exits as a success, and I left it as is, Pine will > just re-run it over the message. If I exit as a failure, Pine's > behaviour's is undefined. Ah. So Pine just sucks. > So, what I've done is have pgpenvelope_decrypt prefix the OpenPGP headers > so looks like: > > #####-----BEGIN PGP MESSAGE----- One "#" might be prettier, and would have the same effect, no? > Changes are in CVS. > > -- > Frank Tobin http://www.uiuc.edu/~ftobin/ > > > > > > -----BEGIN PGPENVELOPE INFORMATION----- > Hash: SHA1 > Version: GnuPG v1.0.1e (FreeBSD) > Comment: pgpenvelope 2.8.7 - http://pgpenvelope.sourceforge.net/ > > gpg: Signature made Sat Jun 24 15:07:23 2000 PDT using DSA key ID 260C4FA3 > gpg: Good signature from "Frank J. Tobin <ft...@bi...>" > gpg: aka "Dekan" > gpg: aka "Frank J. Tobin <ft...@ui...>" > gpg: aka "Frank J. Tobin <ft...@ne...>" > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > gpg: Fingerprint: 4F86 3BBB A816 6F0A 340F 6003 56FF D10A 260C 4FA3 > > pgpenvelope_decrypt: Message processed at Sat Jun 24 15:07:39 2000 > > -----END PGPENVELOPE INFORMATION----- > > > _______________________________________________ > pgpenvelope-users mailing list > pgp...@li... > http://lists.sourceforge.net/mailman/listinfo/pgpenvelope-users > __ L. Sassaman System Administrator | "If you chose not to decide, Technology Consultant | you still have made a choice" icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Rush -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5VTLRPYrxsgmsCmoRAmeAAKCQHQ+cfgVw8iRX11qVqiVBYn3Y/gCgo3TM yljEV6zzrAQXKurmrpdUKko= =RPwM -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-06-24 22:11:37
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 L. Sassaman, at 00:54 -0700 on Sat, 24 Jun 2000, wrote: > Can we have pgpenvelope behave such that when a user selects no to not > decrypt, the message that has been passed to the filter is passed back, > totally unchanged? That would be perfect. I can't leave it 'totally' unchanged, for two reasons. If pgpenvelope_decrypt exits as a success, and I left it as is, Pine will just re-run it over the message. If I exit as a failure, Pine's behaviour's is undefined. So, what I've done is have pgpenvelope_decrypt prefix the OpenPGP headers so looks like: #####-----BEGIN PGP MESSAGE----- Changes are in CVS. - -- Frank Tobin http://www.uiuc.edu/~ftobin/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1e (FreeBSD) Comment: pgpenvelope 2.8.7 - http://pgpenvelope.sourceforge.net/ iEYEARECAAYFAjlVMRsACgkQVv/RCiYMT6PlkACgi6v15nkIpW6MJDHjMeLD/ioO 6CcAnjZLymxnqVpYZLDSygqmlt7D34YU =XKwy -----END PGP SIGNATURE----- |
|
From: L. S. <ra...@qu...> - 2000-06-24 07:58:39
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry for not doing the CVS checkout. Busy busy busy here. One nit about the new "decrypt confirmation" feature... When I proposed it, I wanted a way to be able to easily view the unmolested ciphertext. The current feature does something like this: - -- pgpenvelope_decrypt: confirmation requested Do do you wish to run pgpenvelope over this message? [Y/n] pgpenvelope_decrypt: You have requested not to process this message under pgpenvelope. Pipe command returned error. Hit return to continue. - -- And then returns you to pine with the error message as the only thing on screen. Can we have pgpenvelope behave such that when a user selects no to not decrypt, the message that has been passed to the filter is passed back, totally unchanged? That would be perfect. Thanks, - --Len. On Sun, 11 Jun 2000, Frank Tobin wrote: > If anyone would like to help pgpenvelope 2.8.7 go smoothly (meaning have > no bugs introduced and have the bugs that were supposed to be fixed > actuallly fixed), I ask that you checkout a copy of the current state of > pgpenvelope via CVS, install, and run it. Note: you will likely have to > update Class::MethodMaker to 0.95 to do so (this is because I was using > C::MM wrong before, and recent versions exposed a bug in my code (which > I've fixed), not just because I like people having the latest version of > C::MM). > > Do not install C::MM 0.95 if you have perl 5.005_02 (check "perl -v"). > C::MM does not work perl in this version of perl. This has been > addressed, and 0.96 will work properly on this version of perl (0.96 is > not public yet, but I am in contact with the author). This means that if > you have perl 5.005_02, don't bother trying to get pgpenvelope from CVS. > > Class::MethodMaker 0.95 is available from: > http://www.cpan.org/modules/by-module/Class/Class-MethodMaker-0.95.tar.gz > > Instructions on checking out pgpenvelope from CVS: > https://sourceforge.net/cvs/?group_id=1628 > or > http://sourceforge.net/cvs/?group_id=1628 > (for the SSL-challenged :) ) > > -- > Frank Tobin http://www.uiuc.edu/~ftobin/ > > "To learn what is good and what is to be valued, > those truths which cannot be shaken or changed." Myst: The Book of Atrus > > > _______________________________________________ > pgpenvelope-users mailing list > pgp...@li... > http://lists.sourceforge.net/mailman/listinfo/pgpenvelope-users > __ L. Sassaman System Administrator | "If you chose not to decide, Technology Consultant | you still have made a choice" icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Rush -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5VGk8PYrxsgmsCmoRAlhsAKDTFYjwmV1x6ZrYnO6BQWC4Ia/gtwCeLR8L ylSZxazuaqLVEZUIipQjcBk= =l0Ql -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-06-11 09:46:32
|
If anyone would like to help pgpenvelope 2.8.7 go smoothly (meaning have no bugs introduced and have the bugs that were supposed to be fixed actuallly fixed), I ask that you checkout a copy of the current state of pgpenvelope via CVS, install, and run it. Note: you will likely have to update Class::MethodMaker to 0.95 to do so (this is because I was using C::MM wrong before, and recent versions exposed a bug in my code (which I've fixed), not just because I like people having the latest version of C::MM). Do not install C::MM 0.95 if you have perl 5.005_02 (check "perl -v"). C::MM does not work perl in this version of perl. This has been addressed, and 0.96 will work properly on this version of perl (0.96 is not public yet, but I am in contact with the author). This means that if you have perl 5.005_02, don't bother trying to get pgpenvelope from CVS. Class::MethodMaker 0.95 is available from: http://www.cpan.org/modules/by-module/Class/Class-MethodMaker-0.95.tar.gz Instructions on checking out pgpenvelope from CVS: https://sourceforge.net/cvs/?group_id=1628 or http://sourceforge.net/cvs/?group_id=1628 (for the SSL-challenged :) ) -- Frank Tobin http://www.uiuc.edu/~ftobin/ "To learn what is good and what is to be valued, those truths which cannot be shaken or changed." Myst: The Book of Atrus |
|
From: Frank T. <ft...@ui...> - 2000-06-09 04:37:33
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 L. Sassaman, at 14:36 -0700 on Thu, 8 Jun 2000, wrote: > pgpenvelope is not able to pass decrypted messages to an attached > printer. Test case: I can't test any of this; I don't have a printer. Could you provide me with some details? - -- Frank Tobin http://www.uiuc.edu/~ftobin/ "To learn what is good and what is to be valued, those truths which cannot be shaken or changed." Myst: The Book of Atrus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: pgpenvelope 2.8.6 - http://pgpenvelope.sourceforge.net/ iEYEARECAAYFAjlAc+EACgkQVv/RCiYMT6NQhACfU5WdY8k9PkyFNslaLM1R42jE zgAAn0OzBQlJ3nEON0eK4Iout0rdm4yU =aHqE -----END PGP SIGNATURE----- |
|
From: L. S. <ra...@qu...> - 2000-06-08 21:39:43
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This may be a good thing, but... pgpenvelope is not able to pass decrypted messages to an attached printer. Test case: Receive encrypted email with pine. Decrypt with pgpenvelope. Hit "%" to print to attached printer. pine attempts to refilter the message through pgpenvelope, and pgpenvelope does not properly hand it back to pine for printing. The pine session then freezes in statis, GnuPG error and status messages are sent to the printer, and the user must kill the terminal session to resume work. This is not acceptable. :) Thoughts? - --Len. __ L. Sassaman System Administrator | "It's a nice day Technology Consultant | to start again." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Billy Idol -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5QBHzPYrxsgmsCmoRAhVoAJ9pgRfl/PHa3PeI4FYRrWPcLHeGeACfdkdd T/TADpx9EQSATCLyUHUX9OE= =Z6bR -----END PGP SIGNATURE----- |
|
From: L. S. <ra...@qu...> - 2000-05-01 00:23:12
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 30 Apr 2000, Frank Tobin wrote: > -----BEGIN PGPENVELOPE PROCESSED MESSAGE----- > > L. Sassaman, at 03:25 -0700 on Sun, 30 Apr 2000, wrote: > > > Don't bother. I have fixed it (was a problem in GnuPG::Interface), and > > attached the patch and sig. > > First, it's not good to change GnuPG::Interface so that it doesn't > directly conform to GnuPG, unless it is fixing to to by by the OpenPGP > spec, the goal of GnuPG. GnuPG::Interface is meant to be a strict, > hardcore, no flirts layer over GnuPG, no compatibility issues discussed. > Pathches for compatibility should be put into the products that use it. > BTW, if you were to patch GnuPG, the cleanest way to do so would have been > to edit the default for textmode in GnuPG::Options, but thanks for trying > :) Well, I would think that you would want to be able to call text or binary modes from GnuPG::Interface. It just seems to make more sense to put it in there... > Next, I'm not entirely sure that the --textmode option should be passed > for pgpenvelope. If zip a text file, and then send it to a windows > machine, and then unzip it, no carriage returns 'magically appear'. So I > don't know how I should approach the issue; preferabbly I'd like to know > what 'should' be happening specwise. When specificallly are you having > problems with an absense carriage returns? It is necessary for OpenPGP. Check 7.1 in the current draft. If you don't give it the --textmode option, it does not know that this is a canonical text document, and treats it as a binary doc. I think that 5.2.1 discusses this as well. __ L. Sassaman System Administrator | Technology Consultant | "To hold a pen is to be at war." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Voltaire -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5DMx0PYrxsgmsCmoRAsqDAKDSDrp6DbqU+l5w598ds3PdnYcwaQCcDz2E rY7WxCXbVhxFi6dsvdKkiWo= =8M4v -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-04-30 19:58:38
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 L. Sassaman, at 03:25 -0700 on Sun, 30 Apr 2000, wrote: > Don't bother. I have fixed it (was a problem in GnuPG::Interface), and > attached the patch and sig. First, it's not good to change GnuPG::Interface so that it doesn't directly conform to GnuPG, unless it is fixing to to by by the OpenPGP spec, the goal of GnuPG. GnuPG::Interface is meant to be a strict, hardcore, no flirts layer over GnuPG, no compatibility issues discussed. Pathches for compatibility should be put into the products that use it. BTW, if you were to patch GnuPG, the cleanest way to do so would have been to edit the default for textmode in GnuPG::Options, but thanks for trying :) Next, I'm not entirely sure that the --textmode option should be passed for pgpenvelope. If zip a text file, and then send it to a windows machine, and then unzip it, no carriage returns 'magically appear'. So I don't know how I should approach the issue; preferabbly I'd like to know what 'should' be happening specwise. When specificallly are you having problems with an absense carriage returns? - -- Frank Tobin http://www.uiuc.edu/~ftobin/ "To learn what is good and what is to be valued, those truths which cannot be shaken or changed." Myst: The Book of Atrus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: pgpenvelope 2.8.4 - http://pgpenvelope.sourceforge.net/ iEYEARECAAYFAjkMjnIACgkQVv/RCiYMT6PWzQCffWmMjYqoL49ne6FfvA7IHbVq P5cAoIhd4M4GsGuFjfTybDY0pWS1QTE9 =SHH4 -----END PGP SIGNATURE----- |
|
From: L. S. <ra...@qu...> - 2000-04-30 10:34:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 26 Apr 2000, Frank Tobin wrote: > L. Sassaman, at 20:29 -0700 on Tue, 25 Apr 2000, wrote: > > > The subject says it all. On windows, in the text viewer, messages are > > munged, as though gpg was called without -t. > > Yeah, I remember this problem from before. I'll see what I can do. Don't bother. I have fixed it (was a problem in GnuPG::Interface), and attached the patch and sig. Now you get to name someone in your THANKS file. ;) I created 4 new functions as well, which are really the original four that I changed, renamed without the --textmode option added. I don't believe that GnuPG::Interface is being used by anything other than PGPEnvelope at this time, so this was the easiest way to do things. (Basically, the old functions needed to still be available for signing/encrypting binary files). But regardless, PGPEnvelope works now as soon as you drop in the patched GnuPG::Interface. If you wish to make things a little clearer, you could revert to the original naming for those four "binary" functions, and name the others [..]_text or something along those lines. PGPEnvelope would need to be updated to call the new functions, however. It's up to you. - --Len. __ L. Sassaman System Administrator | Technology Consultant | "To hold a pen is to be at war." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Voltaire -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5DAo5PYrxsgmsCmoRAkB5AKCDT4awCq/kH4NoumCPhwzxhIDpOQCfcQ6R n2x8XXWPb+wHHLKmt+Wz/MY= =p75P -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-04-26 05:10:15
|
L. Sassaman, at 20:29 -0700 on Tue, 25 Apr 2000, wrote: > The subject says it all. On windows, in the text viewer, messages are > munged, as though gpg was called without -t. Yeah, I remember this problem from before. I'll see what I can do. -- Frank Tobin http://www.uiuc.edu/~ftobin/ "To learn what is good and what is to be valued, those truths which cannot be shaken or changed." Myst: The Book of Atrus |
|
From: L. S. <ra...@qu...> - 2000-04-26 03:38:29
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The subject says it all. On windows, in the text viewer, messages are munged, as though gpg was called without -t. Can we fix? __ L. Sassaman System Administrator | Technology Consultant | [This space for rent] icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | -----BEGIN PGP SIGNATURE----- Comment: OpenPGP Encrypted Email Preferred. iD8DBQE5BmLLPYrxsgmsCmoRAub8AKDciZyX9SJrKBkZKYxcIBd8iC+qBACaAhbB 5cuWuQP4B7iWNDwlTXcOvN4= =ZF3F -----END PGP SIGNATURE----- |
|
From: Frank T. <ft...@ui...> - 2000-04-25 14:51:13
|
L. Sassaman, at 02:05 -0700 on Tue, 25 Apr 2000, wrote: > This is generally a bad thing to find in one's procmail log after > installation of PGPEnvelope, no? Crap, yeah. The code tree lost a file when I moved it to sourceforge, it seems, and I didn't notice it. I'll have a new release out soon. -- Frank Tobin http://www.uiuc.edu/~ftobin/ "To learn what is good and what is to be valued, those truths which cannot be shaken or changed." Myst: The Book of Atrus |
|
From: L. S. <ra...@qu...> - 2000-04-25 09:14:03
|
This is generally a bad thing to find in one's procmail log after installation of PGPEnvelope, no? Can't locate PGPEnvelope/Terminal.pm in @INC (@INC contains: /usr/lib/perl5/5.00503/i586-linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i586-linux /usr/lib/perl5/site_perl/5.005 .) at /usr/bin/pgpenvelope_decrypt line 42. BEGIN failed--compilation aborted at /usr/bin/pgpenvelope_decrypt line 42. procmail: Program failure (2) of "/usr/bin/pgpenvelope_decrypt" procmail: Rescue of unfiltered data succeeded |
|
From: - 2000-04-25 09:04:45
|
1299 __ L. Sassaman System Administrator | Technology Consultant | [This space for rent] icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | |
2 messages has been excluded from this view by a project administrator.
