[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: 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.
- Re: solutions, (continued)
- Re: solutions, Nikos Mavrogiannopoulos, 2009/08/04
- Re: solutions, Simon Josefsson, 2009/08/05
- Re: solutions, Nikos Mavrogiannopoulos, 2009/08/05
- Re: solutions, Simon Josefsson, 2009/08/06
- please test imminent 2.8.x release, Simon Josefsson, 2009/08/06
- Re: please test imminent 2.8.x release, Tim Kosse, 2009/08/07
- Re: please test imminent 2.8.x release, Simon Josefsson, 2009/08/10
- Re: please test imminent 2.8.x release, Tomas Hoger, 2009/08/10
- Re: please test imminent 2.8.x release, Simon Josefsson, 2009/08/10
- Re: please test imminent 2.8.x release, Tomas Mraz, 2009/08/10
Re: solutions,
Werner Koch <=