[sylpheed:31299] Re: PGP/MIME-signing breaks sig delimiter

Tatsuya Kinoshita tats at vega.ocn.ne.jp
Sun May 13 03:32:11 JST 2007


On May 11, 2007, [sylpheed:31289],
gstewart (at bonivet.net) wrote:

> > That's the brute-force work-around which defeats the original purpose
> > of the whitespace-stripping. I wonder what exactly the stripping tries
> > to achieve? Is it done just because of the comment in RFC2015?
> 
> It makes you wonder.
> 
> The only relevant mention of the word "space" in the RFC is this:
> 
>      & Also, in some cases it might be desirable to encode any   =20
>      &railing whitespace that occurs on lines in order to ensure  =20
>      & that the message signature is not invalidated when passing =20
>      & a gateway that modifies such whitespace (like BITNET). =20

RFC2015 is updated by RFC3156:

| 3.  Content-Transfer-Encoding restrictions
[...]
|    Additionally, implementations MUST make sure that no trailing
|    whitespace is present after the MIME encoding has been applied.
[...]
|    Data that is ONLY to be encrypted is allowed to contain 8-bit
|    characters and trailing whitespace and therefore need not undergo the
|    conversion to a 7bit format, and the stripping of whitespace.

-- 
Tatsuya Kinoshita


More information about the Sylpheed mailing list