Re: [Samba] chrony configuration for secondary samba DC
- Date: Mon, 4 Jun 2018 17:27:30 +0100
- From: Rowland Penny via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] chrony configuration for secondary samba DC
On Mon, 4 Jun 2018 17:45:20 +0200
Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> On Mon, Jun 04, 2018 at 04:54:36PM +0200, Andreas Schneider wrote:
> > On Monday, 4 June 2018 14:52:34 CEST Rowland Penny wrote:
> > > In ntp.conf you set a line like this:
> > >
> > > restrict default kod nomodify notrap nopeer mssntp
> > >
> > > I cannot find anything that tells me what chrony replaces
> > > 'restrict' with. Is it needed ? is there something that replaces
> > > it, or can you safely ignore it?
> > >
> > > Until all the questions are answered and all the kinks are ironed
> > > out, Samba shouldn't support chrony in the way it does ntp
> > Miroslav, can you explain the missing details?
> I think the important difference between ntpd and chrony wrt to
> ntp_signd is that ntpd has a special restriction for MS-SNTP packets
> (the mssntp option). I think this is because it is generally not
> possible to limit all client access (e.g. servers can always request
> time from ntpd clients) and also to limit addresses that can block
> ntpd as the communication with ntp_signd is synchronous.
> chronyd doesn't make a difference between non-MS-SNTP and MS-SNTP
> packets. There is no blocking due to ntp_signd.
> So, when migrating from ntpd to chrony, all "restrict XXX mssntp"
> lines should have a corresponding "allow XXX" line in chrony.conf.
That is sort of what I thought, but the docs aren't really that
To unsubscribe from this list go to the following URL and read the