Comments in krb5.conf and kdc.conf

[Tom Perrine]

Well, it took me a bit of time to find it, but krb5.conf and
(presumably) kdc.conf *do* have some limited support for comments.

Here is a patch for the administrator's guide.

*** krb5-1.0pl1/krb5-1.0pl1/doc/admin.texinfo.~1~ Tue Dec 24 02:17:48 1996
--- krb5-1.0pl1/krb5-1.0pl1/doc/admin.texinfo Tue Sep 16 11:48:09 1997
***************
*** 370,375 ****
--- 370,378 ----
@end group
@end smallexample

+ A limited comment facility is available; lines with a ';' or '#' as the first character of
+ the line are comments.
+
The @code{krb5.conf} file may contain any or all of the following seven
sections:

--
Tom E. Perrine (t...@SDSC.EDU) | San Diego Supercomputer Center
http://www.sdsc.edu/~tep/ | Voice: +1.619.534.5000
I miss my 36-bit friends: Multics, TOPS-10, and TOPS-20.

[Tom Perrine]

In prof_parse.c:

static errcode_t parse_std_line(line, state)
char *line;
struct parse_state *state;
{
char *cp, ch, *tag, *value;
char *p;
errcode_t retval;
int do_subsection = 0;
void *iter = 0;

if (*line == 0)
return 0;
if (line[0] == ';' || line[0] == '#')
return 0;
strip_line(line);
cp = skip_over_blanks(line);
ch = *cp;

...

--tep

[Ken Hornstein]

>+ A limited comment facility is available; lines with a ';' or '#' as the first ch
>aracter of
>+ the line are comments.
>+

I don't believe '#' is valid; I thought ';' was the only valid comment
character.

--Ken

[Ken Hornstein]

>In prof_parse.c:

And I see that was changed in the most recent release. Whoops, my mistake!
Next time I'll UTSL first.

--Ken