From: david.goldberg6@verizon.net (David S. Goldberg)
Subject: Re: attachments in S/MIME encrypted messages
Date: Mon, 04 Mar 2002 11:43:08 -0500 [thread overview]
Message-ID: <m1blmd89tcz.fsf@blackbird.mitre.org> (raw)
In-Reply-To: <iluelo8yiop.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Fri, 12 Oct 2001 17:36:06 +0200")
>>>>> On Fri, 12 Oct 2001 17:36:06 +0200, Simon Josefsson
>>>>> <jas@extundo.com> said:
Resurecting a dead horse...
> david.goldberg6@verizon.net (David S. Goldberg) writes:
>> I just tried it on XEmacs 21.1.14 under cygwin, which I rarely use or
>> I'd have thought of it before, and it mostly worked right once I got
>> all the cert files properly mirrored on my laptop. The verification
>> process claimed forgery even on messages I sent and signed myself but
>> the resulting article buffer was properly buttonized. I'm in the
>> process of upgrading XEmacs for Solaris to see if that solves the
>> buttonizing problem there, and if so I'll check on the verification
>> thing. I'm running openssl 0.9.5 under cygwin which may be an issue
>> there.
> There _is_ a CRLF bug in Gnus (I just became aware of this), but it is
> in the encoding part, so shouldn't affect this. I have little time to
> look at this now, but hopefully a interoperability testing project
> with the various open mail clients could be started soon, then we
> should be able to detect these problems better.
I finally upgraded to XEmacs 21.4.6. I discovered that there's a new
(or at least newly documented) option to configure called
--with-file-coding which I enabled on Sun (it's on by default under
cygwin) and that solves the CRLF issues. Encrypted emails are
properly parsed under both Sun and cygwin now. I still get a "Sender
address forged" message in the button of a decrypted message in spite
of openssl clearly getting successful verification, but that's much
less of a concern since clicking the button provides me that info.
Thanks,
--
Dave Goldberg
david.goldberg6@verizon.net
next parent reply other threads:[~2002-03-04 16:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0110041538250.14027-100000@lie.extundo.com>
[not found] ` <m1bsncoga19.fsf@blackbird.mitre.org>
[not found] ` <iluelo8yiop.fsf@barbar.josefsson.org>
2002-03-04 16:43 ` David S. Goldberg [this message]
2002-03-04 18:37 ` Simon Josefsson
2002-03-04 20:11 ` Simon Josefsson
2002-03-04 20:11 ` Simon Josefsson
2002-03-04 20:15 ` David S. Goldberg
2002-03-04 20:15 ` David S. Goldberg
2002-03-04 21:00 ` Simon Josefsson
2002-03-05 16:40 ` David S. Goldberg
2002-03-05 17:10 ` David S. Goldberg
2002-03-05 17:10 ` David S. Goldberg
2002-03-05 16:40 ` David S. Goldberg
2002-03-04 21:00 ` Simon Josefsson
2002-03-04 18:37 ` Simon Josefsson
2002-03-04 16:43 ` David S. Goldberg
2001-09-10 14:51 David S. Goldberg
2001-09-10 20:01 ` Simon Josefsson
[not found] ` <m1b1ykryw78.fsf@blackbird.mitre.org>
[not found] ` <iluhetn6rhk.fsf@barbar.josefsson.org>
[not found] ` <m1br8srxela.fsf@blackbird.mitre.org>
2001-09-28 20:28 ` David S. Goldberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1blmd89tcz.fsf@blackbird.mitre.org \
--to=david.goldberg6@verizon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).