From aa96c6cb44a6eeccc506ae055aae2519a7f914e1 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Mon, 29 Apr 2013 18:39:12 -0300 Subject: id128: when taking user input for a 128bit ID, validate syntax Also, always accept both our simple hexdump syntax and UUID syntax. --- man/sd_id128_to_string.xml | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) (limited to 'man/sd_id128_to_string.xml') diff --git a/man/sd_id128_to_string.xml b/man/sd_id128_to_string.xml index ec8b263e0d..593d0752d5 100644 --- a/man/sd_id128_to_string.xml +++ b/man/sd_id128_to_string.xml @@ -59,7 +59,7 @@ int sd_id128_from_string - const char s[33], sd_id128_t* ret + const char* s, sd_id128_t* ret @@ -77,14 +77,19 @@ sd_id128_from_string() implements the reverse operation: it takes a 33 - character array with 32 hexadecimal digits - (terminated by NUL) and parses them back into an - 128 bit ID returned in - ret. + character string with 32 hexadecimal digits + (either lowercase or uppercase, terminated by NUL) and parses them back into an 128 + bit ID returned in + ret. Alternatively, this call + can also parse a 37 character string with a 128bit ID + formatted as RFC UUID. For more information about the sd_id128_t type see - sd-id1283. + sd-id1283. Note + that these calls operate the same way on all + architectures, i.e. the results do not depend on + endianess. When formatting a 128 bit ID into a string it is often easier to use a format string for -- cgit v1.2.3-54-g00ecf