Re: signed/encrypted messages with attachments...

[Josh Huber <huber@alum.wpi.edu>]

Simon Josefsson <simon@josefsson.org> writes:

> Josh Huber <huber@alum.wpi.edu> writes:
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="==-=-="

Yeah, this definately doesn't look right :)  The headers got mixed in
with the body of the MIME part.

> It should work, does it not?  Let's see, I'll attach a dummy file and
> sign this mail..  *previewing it* No, this doesn't look right, only
> the text was signed.  Well, you can add "sign=pgpmime" to the
> attachment MML tag as well, but then you'll get two multipart/signed
> structures, which probably no other mail reader than Gnus would
> handle.

Right, I think mutt does this correctly.  For example, a signed
message I received has the following structure:

(headers)
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="Pd0ReVV5GZGQvF3a"
Content-Disposition: inline

...

(body)

--Pd0ReVV5GZGQvF3a
Content-Type: multipart/mixed; boundary="6c2NcOVqGQ03X4Wi"
Content-Disposition: inline

--6c2NcOVqGQ03X4Wi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

[text here]

--6c2NcOVqGQ03X4Wi
Content-Type: text/x-csrc; charset=us-ascii
Content-Disposition: attachment; filename="foo.c"
Content-Transfer-Encoding: quoted-printable

[attached c file here]

--6c2NcOVqGQ03X4Wi--

--Pd0ReVV5GZGQvF3a
Content-Type: application/pgp-signature
Content-Disposition: inline

[pgp signature here]

--Pd0ReVV5GZGQvF3a--


> Ah, you can do:
> 
> <$mml sign=pgpmime>
> text...
> <$part filename="~/foo">
> 
> and then you only get one top-level multipart/signed part containing a
> multipart/mixed part with the text and the file.  But somehow the
> attribution ("Josh Huber <huber@alum.wpi.edu> writes:") ends up inside
> MIME headers.  Perhaps this breaks the signature as well.  Let's see..

Well, I don't know, because your signature doesn't seem to be
available from the keyservers.  oh well.

the message was definately screwed up, though.

anyone who's a little more familiar with the mml gnus code have any
ideas here?  If not, i'll take a look myself...

-- 
Josh Huber