[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: solutions

From: Werner Koch
Subject: Re: solutions
Date: Tue, 04 Aug 2009 10:31:46 +0200
User-agent: Gnus/5.110011 (No Gnus v0.11)

On Mon,  3 Aug 2009 23:38, address@hidden 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: (invalid encoded OID).
You may want to use a similar hack.



Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]