Re: [chrony-users] Disabling peers+dmpeers+monlist |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Disabling peers+dmpeers+monlist
- From: Dominik Vogt <dominik.vogt@xxxxxx>
- Date: Mon, 12 Oct 2020 22:39:54 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1602538798; bh=zWW0azg+IEwf9drZar76o2fviqM1e1nxBUaIWnh0TBM=; h=X-UI-Sender-Class:Date:From:To:Subject:Reply-To:References: In-Reply-To; b=RIsfEVt0RPIPAsAqXanu6jwiircMKRfD3vijcSq+xeMYbf47OWq/0I0Y8kvA99NzD vZyVVEn/UbPwSqkJQx0iZTJYPyR32JW7IacqqQnBndEkOebEZbIPaqYLm/BQOcyMH+ j1y/ji8Os8dqmR2FGimVkb/7U5bkbLg3Sl1Fe2uI=
On Mon, Oct 12, 2020 at 09:58:31AM -0700, Bill Unruh wrote:
> Do those "security manuals" explain what the problem is that they are trying
> to solve by these disablings?
No, unfortunately not, at least not the requirements we have for
our project. All I know is that they come from some european
security standard, so it's most likely some well known issue.
> I suspect even in ntpd what they mean is that these commands should not be
> turned on, rather than exlicitly disabled. Ie, the sysadmin must explicitly
> enable them rather than explicitly disable them. monlist seems to report all
> of the past connection sources, which means that a
> request from such a server can return far more data than was in the request.
> This opens a denial of service attack possiblity. (You send a short packet,
> they send a whole gob of material tying up the network.)
>
> I suspect both others are similar. So this has to do with the remote query
> abilities of ntpd.
Sounds legible, but I can only guess whether using chrony instead
of ntpd fulfils the requirements or if extra work has to be spent.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.