Re: Retiring ntp

2020-11-03 Thread Miroslav Lichvar
On Mon, Nov 02, 2020 at 09:52:59PM +, Gary Buhrmaster wrote: > On Mon, Nov 2, 2020 at 9:36 PM Nico Kadel-Garcia wrote: > > > So, use "chrony" instead? > > For some use cases, there is also the option of > systemd-timesyncd as a ntp client. timesyncd is a very minimal NTP client. It can be r

Re: Retiring ntp

2020-11-03 Thread Tomasz Torcz
On Mon, Nov 02, 2020 at 11:58:53PM -0600, Alex Thomas wrote: > Question : I know that FreeIPA at one point did not work well with > chrony and required the installation of ntp. This might cause an > issue. That's not a problem anymore. Support for chrony was added in 4.7.0, released in 2018, so

Re: Retiring ntp

2020-11-02 Thread Alex Thomas
Question : I know that FreeIPA at one point did not work well with chrony and required the installation of ntp. This might cause an issue. On Mon, Nov 2, 2020 at 3:54 PM Gary Buhrmaster wrote: > > On Mon, Nov 2, 2020 at 9:36 PM Nico Kadel-Garcia wrote: > > > So, use "chrony" instead? > > For som

Re: Retiring ntp

2020-11-02 Thread Gary Buhrmaster
On Mon, Nov 2, 2020 at 9:36 PM Nico Kadel-Garcia wrote: > So, use "chrony" instead? For some use cases, there is also the option of systemd-timesyncd as a ntp client. > Is the functionality sufficient As always, given the different use cases, the answer is maybe. Here is a quick comparison: h

Re: Retiring ntp

2020-11-02 Thread Nico Kadel-Garcia
On Mon, Nov 2, 2020 at 9:33 AM Miroslav Lichvar wrote: > > I think we should consider retiring the ntp package. The upstream > project is not in a good shape and it doesn't seem to be improving. > Contributors left long time ago. The development is slow and happens > behind closed doors. They stil

Re: Retiring ntp

2020-11-02 Thread Subsentient
I don't have objections to retiring the ntp tool, as long as there's something to take its place, and as long as a command argument compatible ntpdate tool still exists. I tend to use ntpdate much more often than I enable the ntp service. Right now ntpdate runs on boot on my PinePhone's Fedora 3

Re: Retiring ntp

2020-11-02 Thread Miroslav Lichvar
On Mon, Nov 02, 2020 at 06:09:18PM +0100, Björn Persson wrote: > Miroslav Lichvar wrote: > > The main problem is that they don't fix all known security issues. In > > the CVE list I see about 10 issues that were not fixed at all or only > > partially, some exploitable in default configuration. >

Re: Retiring ntp

2020-11-02 Thread Neal Gompa
On Mon, Nov 2, 2020 at 12:37 PM PGNet Dev wrote: > > On 11/2/20 9:22 AM, Neal Gompa wrote: > > Work migrated to Chrony a year or so ago. The only thing I use from > > ntp is the "ntpdate" tool. Everything else is chrony now. :) > > out of curiosity, what's lacking for your use case? > > ntpdate, h

Re: Retiring ntp

2020-11-02 Thread PGNet Dev
On 11/2/20 9:22 AM, Neal Gompa wrote: Work migrated to Chrony a year or so ago. The only thing I use from ntp is the "ntpdate" tool. Everything else is chrony now. :) out of curiosity, what's lacking for your use case? ntpdate, here, was primarily for "set it now" interventions. that, at leas

Re: Retiring ntp

2020-11-02 Thread Neal Gompa
On Mon, Nov 2, 2020 at 12:10 PM Björn Persson wrote: > > Miroslav Lichvar wrote: > > The main problem is that they don't fix all known security issues. In > > the CVE list I see about 10 issues that were not fixed at all or only > > partially, some exploitable in default configuration. > > That so

Re: Retiring ntp

2020-11-02 Thread Björn Persson
Miroslav Lichvar wrote: > The main problem is that they don't fix all known security issues. In > the CVE list I see about 10 issues that were not fixed at all or only > partially, some exploitable in default configuration. That sounds bad. Where is that list? In Red Hat Bugzilla I see only two.

Re: Retiring ntp

2020-11-02 Thread Steven A. Falco
On 11/2/20 10:37 AM, Miroslav Lichvar wrote: On Mon, Nov 02, 2020 at 10:14:05AM -0500, Steven A. Falco wrote: I use ntp heavily for multiple stratum 1 timeservers here. If you drop ntp, I will have to build my own from source. Not a big problem, but I'd personally like to see ntp stay availa

Re: Retiring ntp

2020-11-02 Thread Miroslav Lichvar
On Mon, Nov 02, 2020 at 04:09:33PM +0100, Reindl Harald (privat) wrote: > Am 02.11.20 um 15:33 schrieb Miroslav Lichvar: > > In Fedora, there seems to be only one package that has a dependency on > > ntp: nagios-plugins-ntp-perl. It's a monitoring plugin using the > > problematic mode-6 protocol. I

Re: Retiring ntp

2020-11-02 Thread Miroslav Lichvar
On Mon, Nov 02, 2020 at 10:14:05AM -0500, Steven A. Falco wrote: > I use ntp heavily for multiple stratum 1 timeservers here. If you drop ntp, > I will have to build my own from source. Not a big problem, but I'd > personally like to see ntp stay available in Fedora. I have few stratum-1 serve

Re: Retiring ntp

2020-11-02 Thread Steven A. Falco
On 11/2/20 10:23 AM, Tomasz Torcz wrote: On Mon, Nov 02, 2020 at 10:14:05AM -0500, Steven A. Falco wrote: On 11/2/20 9:33 AM, Miroslav Lichvar wrote: I'm not sure how many users of ntp are there. As a replacement, we could package ntpsec. It is an actively maintained fork of ntp which has remov

Re: Retiring ntp

2020-11-02 Thread Tomasz Torcz
On Mon, Nov 02, 2020 at 10:14:05AM -0500, Steven A. Falco wrote: > On 11/2/20 9:33 AM, Miroslav Lichvar wrote: > > I'm not sure how many users of ntp are there. As a replacement, we > > could package ntpsec. It is an actively maintained fork of ntp which > > has removed a lot of code and fixed or a

Re: Retiring ntp

2020-11-02 Thread Steven A. Falco
On 11/2/20 9:33 AM, Miroslav Lichvar wrote: I think we should consider retiring the ntp package. The upstream project is not in a good shape and it doesn't seem to be improving. Contributors left long time ago. The development is slow and happens behind closed doors. They still use bitkeeper. Th

Re: Retiring ntp

2020-11-02 Thread Neal Gompa
On Mon, Nov 2, 2020 at 9:33 AM Miroslav Lichvar wrote: > > I think we should consider retiring the ntp package. The upstream > project is not in a good shape and it doesn't seem to be improving. > Contributors left long time ago. The development is slow and happens > behind closed doors. They stil