Could you explain how the following detached signature would be
encoded using RFC1847/RFC2015? Would you use multipart/signed or
multipart/encrypted?
multipart/signed, with no encoding for clear text. For opaque signing we
could either encode it with base64 or sign & encrypt.
An example:
From: Hal Finney <hal(_at_)rain(_dot_)org>
To: Lindsay Mathieson <lindsay(_at_)powerup(_dot_)com(_dot_)au>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary=bar; micalg=pgp-md5;
protocol="application/pgp-signature"
--bar
Content-Type: text/plain; charset=iso-8859-1
Lindsay Mathieson, <lindsay(_at_)powerup(_dot_)com(_dot_)au>, writes,
quoting me:
> > - There is no PGP/MIME encoding of a detached signature
> >
> > - There is no PGP/MIME encoding of a non-clear signed message
>
> ? Both points are clearly addressed (and doable) in RFC 1847 &
RFC2015, which
> are PGP/MIME (aren't they ?)
Could you explain how the following detached signature would be
encoded using RFC1847/RFC2015? Would you use multipart/signed or
multipart/encrypted?
--bar
Content-Type: application/pgp-signature
-----BEGIN PGP MESSAGE-----
Version: PGP for Personal Privacy 5.0
iQA/AwUBNH5DH7qVexb8FGk/EQKTagCg9NwSygbmXdVts7NbIyPkaX9p65QAn2Lu
DTwZos6GWUDnplXYbZXolxLY
=hgt3
-----END PGP MESSAGE-----
--bar--
--
Lindsay Mathieson
Black Paw Communications
Using MailCat for Win32 Beta Vs 2.6.1.2, on November 29, 1997, in Win95
4.0
http://www.blackpaw.com/