Re: How krb5.conf is parsed (especially in respect to comments)
Harald Barth <[email protected]> Tue, 27 Mar 2018 01:05:24 +0200 (CEST)
| Newsgroups | gmane.comp.encryption.kerberos.heimdal.general |
|---|---|
| Message-ID | <[email protected]> |
> No, the docs are wrong.
OK.
I found that "renew_lifetime = 3 days" actually works but
"renew_lifetime = 3 days " does not. Difficult to see.
So I think in parse_something() this fixes it:
$ diff -u parse_units.c{.orig,}
--- parse_units.c.orig 2017-07-11 07:14:16.000000000 +0200
+++ parse_units.c 2018-03-27 00:44:20.800540496 +0200
@@ -135,6 +135,8 @@
}
if (*p == 's')
++p;
+ while(isspace((unsigned char)*p))
+ ++p;
}
return res;
}
>> Probably the documentation, kinit and verify_krb5_conf should agree
>> about the format.
verify_krb5_conf seems to strip trailing space before giving it to parse_time()
This in config_file.c:parse_binding() looks suspicious:
while(p > p1 && isspace((unsigned char)*(p-1)))
--p;
Harald.