Range checking on config file
Eric S. Raymond
esr at thyrsus.com
Tue Jan 2 10:32:36 UTC 2018
Hal Murray via devel <devel at ntpsec.org>:
>
> Unless I missed something, the code processing gonfig slots can't distinguish
> -1 from 0xffffffff or the equivalent decimal number.
> They both come through as T_Integer. There is no T_Unsigned
>
> The checking code gets to pull it as either xx->val.i or xx->val.u
> struct attr_val_tag {
> attr_val * link;
> int attr;
> int type; /* T_String, T_Integer, ... */
> union val {
> int i;
> unsigned int u;
> int_range r;
> double d;
> char * s;
> } value;
> };
That is correct. Is this leading to a bug?
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
More information about the devel
mailing list