On Tue, Jul 25, 2017 at 08:37:18AM +0200, Miroslav Lichvar wrote:
> On Mon, Jul 24, 2017 at 08:24:57PM +0000, Parker, Michael D. wrote:
> > The chrony allow directive allows the addition of a symbolic hostname in its
> > specification. However, I took a leap in entering the following directive:
> > 
> > allow hostname/16
> > 
> > which failed to do what I expected but no configuration file error was
> > flagged.
> 
> This is not supported. If allow/deny has a hostname, it always applies
> to all 32 (for IPv4) or 128 bits (for IPv6).

At least for now, I'll fix the parser to not allow slashes after
hostnames in the allow/deny directives/commands.

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Reply via email to