Date: Fri, 03 Jun 2016 14:34:18 -0400 From: Lowell Gilbert <freebsd-security-local@be-well.ilk.org> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: stable@freebsd.org, freebsd-security@freebsd.org Subject: Re: unbound and ntp issuse Message-ID: <44lh2mi0k5.fsf@lowell-desk.lan> In-Reply-To: <20160602122727.GB75625@zxy.spb.ru> (Slawa Olhovchenkov's message of "Thu, 2 Jun 2016 15:27:27 %2B0300") References: <20160602122727.GB75625@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Slawa Olhovchenkov <slw@zxy.spb.ru> writes:
> Default install with local_unbound and ntpd can't be functional with
> incorrect date/time in BIOS:
>
> Unbound requred correct time for DNSSEC check and refuseing queries
> ("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed to prime
> trust anchor -- DNSKEY rrset is not secure . DNSKEY IN")
>
> ntpd don't have any numeric IP of ntp servers in ntp.conf -- only
> symbolic names like 0.freebsd.pool.ntp.org, as result -- can't
> resolve (see above, about DNSKEY).
I can't see how this would happen. DNSSEC doesn't seem to be required in
a regular install as far as I can see. Certainly I don't have any
problem on any of my systems, and I've never configured an anchor on the
internal systems.
> IMHO, ntp.conf need to include some numeric IP of public ntp servers.
Ouch; that's a terrible idea, for several different reasons.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44lh2mi0k5.fsf>