Re: dash-escaped text in GPG -> RFC2440

* Andreas Krennmair <ak@synflood.at> [2003-07-18 10:47]:
> > um gottes willen, denken die leute eigentlich nicht nach?
> > was is so kompliziert daran nach dem ganzen string
> > "-----BEGIN PGP SIGNATURE-----" zu suchen?
>
> Siehe RFC 2440, Section 7.1

ja, es sit sogar "in stein gemeisselt". *seufz*

> Mail-Followup-To: Andreas Krennmair <ak@synflood.at>,
> Martin Baehr <mbaehr@email.archlab.tuwien.ac.at>,
> linuxevent@mlist.Austria.EU.net

ist das absicht?

Sven [antwortet nur auf die liste]

------------------------------------------------------------------------
RFC 2440 OpenPGP Message Format November 1998

7.1. Dash-Escaped Text

   The cleartext content of the message must also be dash-escaped.

   Dash escaped cleartext is the ordinary cleartext where every line
   starting with a dash '-' (0x2D) is prefixed by the sequence dash '-'
   (0x2D) and space ' ' (0x20). This prevents the parser from
   recognizing armor headers of the cleartext itself. The message digest
   is computed using the cleartext itself, not the dash escaped form.

   As with binary signatures on text documents, a cleartext signature is
   calculated on the text using canonical <CR><LF> line endings. The
   line ending (i.e. the <CR><LF>) before the '-----BEGIN PGP
   SIGNATURE-----' line that terminates the signed text is not
   considered part of the signed text.

   Also, any trailing whitespace (spaces, and tabs, 0x09) at the end of
   any line is ignored when the cleartext signature is calculated.
.

[ Um sich von dieser Liste abzumelden, sende bitte "unsubscribe" ]
[ an <linuxevent-request@mlist.austria.eu.net>. ]
Received on Fri Jul 25 12:18:11 2003