[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: PGP/MIME (RFC 2015) support?
From:       Espen Sand <espensa () online ! no>
Date:       2000-06-03 22:02:38
[Download RAW message or body]

On Sat, 03 Jun 2000, Joshua Haberman wrote:
> On 06/04, Don Sanders wrote:
> > > Hello, I don't use KMail, but I was recently corresponding with someone
> > > who does. Why is it that KMail doesn't encrypt mail according to the RFC
> > > 2015 spec? Seeing that encryption and decryption are already supported,
> > > why not change the few neccesary headers to make it compliant
> > 
> > Can you please give details of the few necessary changes required?
> 
> You can read the full RFC at
> http://andrew2.andrew.cmu.edu/rfc/rfc2015.html (it's not long), but I'll
> summarize here:
> 
> For Encrypted Data:
>     1. set MIME Content-Type header to "multipart/encrypted"
>     2. set "protocol" parameter to "application/pgp-encrypted"
>     3. Encrypted data must consist of two MIME body parts:
>         i.  first part is control block, contains any control information
>             (which is very scant, as PGP metadata is mostly
>             self-contained). Must have Content-Type of "application/pgp-
>             encrypted"
>         ii. second part is the actual encrypted data (ie, just insert
>             the ASCII-armored PGP block. Must have Content-Type of
>             "application/octet-stream"
> 
> There are similar requirements for signed data...
> 
> If no one's planning on implementing this, I'd be happy to jump in and
> give it a try. It seems mostly a matter of logistics, most of the work
> is already done.

I can only say for myself that it would be nice if you could do it since 
you probaly know what is needed better than anyone else.


-- 
Espen Sand

[prev in list] [next in list] [prev in thread] [next in thread]