W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > April to June 2001

Re: AW: AW: KeyName white space

From: Tom Gindin <tgindin@us.ibm.com>
Date: Tue, 15 May 2001 07:36:47 -0400
To: "Gregor Karlinger" <gregor.karlinger@iaik.at>
Cc: <w3c-ietf-xmldsig@w3.org>
Message-ID: <OFD172339F.EF263ACF-ON85256A4D.003F83D3@somers.hqregion.ibm.com>

     I would like to require the escaping of all ASCII controls in DN's in
XMLDSIG (I was not precise enough last time, and what I said could have
been interpreted as having wider scope) because otherwise standard trimming
routines may eliminate characters which somebody left in a DN
intentionally, as is permitted by RFC 2253.  It is my impression that
standard trimming routines tend to remove horizontal tab, for example, in
the same positions where they remove space.

          Tom Gindin

"Gregor Karlinger" <gregor.karlinger@iaik.at> on 05/15/2001 07:10:53 AM

To:   Tom Gindin/Watson/IBM@IBMUS
cc:   <w3c-ietf-xmldsig@w3.org>
Subject:  AW: AW: KeyName white space



> require it to start with an alphanumeric, trimming any leading whitespace
> would be safest.

Yes, and this requirement should be stated in XML-Signature.

>      So I think considering unescaped spaces at either end of a DN to be
> part of it is actually in violation of RFC 2253.  However, and very
> strangely, no similar requirement exists for horizontal tab or line feed,
> while carriage return must be escaped according to RFC 1779 but not 2253.
> Should we require that XMLDSIG implementations escape all ASCII control
> characters as well?

Why would you like to require such an escaping?

Liebe Gruesse/Regards,
DI Gregor Karlinger
Phone +43 316 873 5541
Institute for Applied Information Processing and Communications
Received on Tuesday, 15 May 2001 07:37:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:10:04 UTC