Project

General

Profile

Bug #96

Invalid character (null 0x00) in certificate URL

Added by Allen Bailey almost 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
charon
Target version:
Start date:
15.10.2009
Due date:
Estimated time:
Affected version:
5.9.0
Resolution:

Description

Using HASH_AND_URL of X509 certificate. Per ABNF description in RFC3986, 0x00 is not an acceptable character in the path. However, the URL that is generated seems to have a terminating null character in the certificate payload:

Oct 9 17:11:18 swlinux2 charon: 15[ENC] generating rule 11 CERT_DATA
...
2F 65 62 ............./eb
charon: 15[ENC] 80: 61 34 62 61 65 61 62 36 66 61 65 64 33 34 39 32 a4baeab6faed3492
charon: 15[ENC] 96: 35 38 39 39 32 32 66 62 32 30 63 34 38 32 38 62 589922fb20c4828b
charon: 15[ENC] 112: 36 37 33 32 37 33 00 673273.

History

#1 Updated by Andreas Steffen almost 11 years ago

  • Target version changed from 4.3.3 to 4.3.5

#2 Updated by Martin Willi almost 11 years ago

  • Status changed from New to Closed

RFC4306 is not really clear about NULL-terminating URLs in Hash-and-URL payloads. But as the length of the URL is obvious, encoding without a NULL probably makes more sense.

Fixed in 1eab115a.

Also available in: Atom PDF