solutions

[Werner Koch]

On Mon,  3 Aug 2009 23:38, simon at josefsson.org said:

> However, isn't this the wrong way to address the real problem?  It seems
> callers of the function should be fixed to be careful not to assume
> decoded data does not contain NULs?

This is often hard to implement.

FWIW, Libksba uses an rfc-2253 representation of DNs in its API, thus
there is no problem due to the required quoting.  However, for bad
(well, unlikely) encodings of URLs, Libksba now uses a made up OID to
indicate this error:  1.3.6.1.4.1.11591.2.12242973 (invalid encoded OID).
You may want to use a similar hack.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.