Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon

There is still a Mismatched SOCK filespec implemented by chronyd and chronyc. The saving grace was that loopback network interface hid this bug very well and saved the day for nearly everyone (who is not an expert Chronyd configurer)... That is, until the directive 'cmddeny 127.0.0.1' is

Bug#995260: closed by Vincent Blut (Re: Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon)

so why did it not use the Unix socket but fell back to 127.0.0.1 approach? i wonder what happens if i do ‘cmddeny all’?

Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon

Hi, Le 2021-09-28 11:55, Steve Egbert a écrit : > Package: chrony > Version: 4.0-8 > Severity: grave > Tags: upstream > Justification: renders package unusable > X-Debbugs-Cc: s.egb...@sbcglobal.net > > Dear Maintainer, > > > The filename construct for a UNIX socket to be shared > between the

Bug#995260: chrony: Mismatched filename for UNIX socket between client and daemon

Package: chrony Version: 4.0-8 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: s.egb...@sbcglobal.net Dear Maintainer, The filename construct for a UNIX socket to be shared between the Chrony (chronyd) daemon and its Chrony CLI (chronyc) client admin tool