Le 2024-04-25 09:13, Miroslav Lichvar a écrit :
> On Wed, Apr 24, 2024 at 04:46:07PM +0200, Vincent Blut wrote:
> > The failing tests that initiated this thread are now fixed, however
> > 002-largenetwork
> > still fails though.
>
> I think that's the arm emulation
Le 2024-04-24 12:17, Miroslav Lichvar a écrit :
> On Thu, Apr 18, 2024 at 07:07:33PM +0200, Vincent Blut wrote:
> > Le 2024-04-18 17:19, Miroslav Lichvar a écrit :
> > > On Thu, Apr 18, 2024 at 04:06:54PM +0200, Vincent Blut wrote:
> > > > So after building clknet
Le 2024-04-18 17:19, Miroslav Lichvar a écrit :
> On Thu, Apr 18, 2024 at 04:06:54PM +0200, Vincent Blut wrote:
> > > The log shows that clknetsim is not built with the -D_LARGEFILE_SOURCE
> > > -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 flags. It needs to use the same
> &
Hi,
Le 2024-04-16 08:08, Miroslav Lichvar a écrit :
> On Tue, Apr 16, 2024 at 12:25:53AM +0200, Vincent Blut wrote:
> > I have yet to set up an armhf based environment to properly debug those
> > failures,
> > but the most likely cause seems to be the ongoing migrati
Hi Miroslav,
I'm experiencing some issues with 4 simulation tests¹ on the armel and armhf
architectures:
SUMMARY:
TOTAL 63
PASSED 59
FAILED 4(008-ntpera 115-cmdmontime 139-nts 145-rtc) (24508 24508 24508
24508)
SKIPPED 0 ()
I have yet to set up an armhf based environment to
Hi,
Currently, 'chronyd -p' can read fragmented configuration files specified by
the 'include' directive and those from the directories specified by the
'confdir' directive.
I had a bug report [1] from a user who wants 'chronyd -p' to also print NTP
sources specified in .sources files. What's
Hi,
Le 2022-01-11 10:07, Miroslav Lichvar a écrit :
> On Mon, Jan 10, 2022 at 03:34:28PM +0100, Vincent Blut wrote:
> > SUMMARY:
> > TOTAL 1
> > PASSED 0
> > FAILED 1(008-ntpera) (24505)
> > SKIPPED 0 ()
> >
> > Do you have any tips on
Hi Miroslav,
This test fails reproducibly with chrony 4.2 and clknetsim HEAD in a Debian
LXC testbed. The error seems to happen in the second inner for loop.
For the test to pass, we expect that the "check_sync" function returns 1.
It does not here since the check_stat function returns 0 (i.e.
Le 2021-11-16 12:04, Miroslav Lichvar a écrit :
> On Thu, Jan 28, 2021 at 03:40:52PM +0100, Miroslav Lichvar wrote:
> > I guess most people here don't follow the NTP WG list. There is one
> > feature proposed for NTPv5 that I think would make a big difference
> > for chrony:
> >
> >
On 2020-10-02T16:15+0200, Vincent Blut wrote:
Hello,
On 2020-10-01T16:57+0200, Vincent Blut wrote:
Hi,
On 2020-10-01T16:41+0200, Miroslav Lichvar wrote:
The NTS specification (RFC 8915) has been published, so I think it
would be a good time to make the final release. Unless anything major
On 2020-10-01T17:07+0200, Miroslav Lichvar wrote:
On Thu, Oct 01, 2020 at 04:57:36PM +0200, Vincent Blut wrote:
Hi,
On 2020-10-01T16:41+0200, Miroslav Lichvar wrote:
> The NTS specification (RFC 8915) has been published, so I think it
> would be a good time to make the final release.
Hi,
On 2020-10-01T16:41+0200, Miroslav Lichvar wrote:
The NTS specification (RFC 8915) has been published, so I think it
would be a good time to make the final release. Unless anything major
shows up, I'll make it on Monday. If anyone has any forgotten bug
reports, or was planning to do some
On 2020-09-01T14:30+0200, Miroslav Lichvar wrote:
On Tue, Sep 01, 2020 at 02:08:06PM +0200, Vincent Blut wrote:
Hi Miroslav,
On 2020-09-01T12:11+0200, g...@tuxfamily.net wrote:
> commit 9ca250755f139c2383ada58198ecfcd7a22954a1
> Author: Miroslav Lichvar
> Date: Mon Aug 31 15:1
system trusted
certificates due to p11-kit >= 0.23.21 getting the program name from
/proc/self/exe.
readlinkat() should be added for arm64 and riscv64, then. Patch
attached.
Cheers,
Vincent
From 9917844fb0ac2a588ca77f3b0c36b371125e012e Mon Sep 17 00:00:00 2001
From: Vincent Blut
D
On 2020-08-26T20:02+0200, Miroslav Lichvar wrote:
On Wed, Aug 26, 2020 at 03:42:17PM +0200, Vincent Blut wrote:
True! But some admins/users may have overridden the default PID file
location where the _chrony system user have write access. If so, let’s
protect them from this vulnerability
On 2020-08-26T15:30+0200, Miroslav Lichvar wrote:
On Wed, Aug 26, 2020 at 03:15:48PM +0200, Vincent Blut wrote:
Miroslav, Matthias, thanks a lot for working on this.
I backported this patch to chrony 3.0 for our previous stable release
(Debian 9). Would someone please check that everything
Hey there,
On 2020-08-20T08:55+0200, g...@tuxfamily.net wrote:
This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.
The annotated tag, 3.5.1 has been created
at 571a7971cad5537a0e98a3c90aa0b02f5d047c3f (tag)
On 2019-03-27T14:31+0100, Miroslav Lichvar wrote:
On Wed, Mar 27, 2019 at 08:23:13AM -0500, Lonnie Abelbeck wrote:
> On Mar 27, 2019, at 6:22 AM, Miroslav Lichvar wrote:
>
> I've been working on an implementation of the new NTP public-key
> authentication called Network Time Security (NTS).
On 2020-05-14T15:35+0200, Miroslav Lichvar wrote:
On Thu, May 14, 2020 at 03:26:20PM +0200, Vincent Blut wrote:
#ifdef __NR_clock_gettime64
SCMP_SYS(clock_gettime64),
#endif
would fly for you‽
Yes.
By the way, shouldn’t we add *time64 variants to some of our already
whistelisted
On 2020-05-14T11:15+0200, Miroslav Lichvar wrote:
On Thu, May 14, 2020 at 09:15:31AM +0200, Miroslav Lichvar wrote:
On Wed, May 13, 2020 at 09:40:07PM +0200, Vincent Blut wrote:
> Hi Miroslav,
>
> We got a bug reportÃâù showing that chronyd might not start correctly,
On 2020-05-12T09:05+0200, Miroslav Lichvar wrote:
On Mon, May 11, 2020 at 07:05:21PM +0200, Vincent Blut wrote:
From a quick glance, the rest seems to make sense.
There is an issue with the Unix domain socket that I missed before. It
would need to be bound and have the owner changed before
Hi,
On 2020-04-28T10:26+0200, Miroslav Lichvar wrote:
On Mon, Apr 27, 2020 at 10:12:59PM +0200, Vincent Blut wrote:
$ getfacl /run/chrony 2>/dev/null
# file: run/chrony
# owner: _chrony
# group: _chrony
user::rwx
group::r-x
other::---
Nonetheless, from a security point of view, wo
Hi,
While preparing chrony 4.0-pre1 for Debian experimental, I observed that
stopping chronyd throws the following error:
chronyd[118401]: Could not remove /run/chronyd.pid : Permission denied
I have yet to look for where the issue lies but as I’m unable to
reproduce this with chrony 3.5,
().
Cheers,
Vincent
From a92cd18bd025add6ff99c0f8dd719d2ee5b7d922 Mon Sep 17 00:00:00 2001
From: Vincent Blut
Date: Thu, 16 Jan 2020 17:04:35 +0100
Subject: [PATCH] sys_linux: allow renameat2 in seccomp filter
This is needed for architectures that support neither rename() nor
renameat() (e.g. riscv64
On 2019-12-11T16:13+0100, Christian Ehrhardt wrote:
On Tue, Dec 10, 2019 at 5:59 PM Miroslav Lichvar
wrote:
On Tue, Dec 10, 2019 at 04:25:31PM +0100, Christian Ehrhardt wrote:
> On Tue, Dec 10, 2019 at 4:19 PM Miroslav Lichvar
> > I'm sorry for changing my mind, but I now think this case
On 2019-12-10T15:52+0100, Christian Ehrhardt wrote:
The test might run on different platforms.
If the platform happens to have a RTC that does exist but unable to
have RTC_UIE_ON set the test will fall into an infinite hang.
Exampls of bad clocks are:
- ppc64el: rtc-generic
- arm64: rtc-efi
To
On 2019-12-06T16:55+0100, Vincent Blut wrote:
On 2019-12-06T10:21+0100, Christian Ehrhardt wrote:
Hi chrony-dev,
chrony is tested in Debian/Ubuntu on any update of related packages
and while that was running I found that arm64 and ppc64 reproducibly
hang [1][2]. OTOH arm64 and s390x
On 2019-12-06T10:21+0100, Christian Ehrhardt wrote:
Hi chrony-dev,
chrony is tested in Debian/Ubuntu on any update of related packages
and while that was running I found that arm64 and ppc64 reproducibly
hang [1][2]. OTOH arm64 and s390x reproducibly work.
By the way, I just gave it a shot on
On 2019-12-06T12:35+0100, Christian Ehrhardt wrote:
>
> Could that be due to the use of “-x”? IFAIR you have extra stuff on
> Ubuntu about that option.
I was testing the current master tarball from upstream to avoid any confusion.
=>
Hi Christian,
On 2019-12-06T10:21+0100, Christian Ehrhardt wrote:
Hi chrony-dev,
chrony is tested in Debian/Ubuntu on any update of related packages
and while that was running I found that arm64 and ppc64 reproducibly
hang [1][2]. OTOH arm64 and s390x reproducibly work.
^
Hi,
Please accept the following patch to fix a typo in the chrony.conf man
page.
Good day,
Vincent
From f9869e568b6f9572f5a3747d2fb25efadb9e5a5c Mon Sep 17 00:00:00 2001
From: Vincent Blut
Date: Thu, 28 Nov 2019 16:06:45 +0100
Subject: [PATCH] doc: fix typo in chrony.conf man page
---
doc
On Mon, Mar 18, 2019 at 02:29:40PM +0100, Miroslav Lichvar wrote:
On Fri, Mar 15, 2019 at 03:29:10PM +0100, Vincent Blut wrote:
On Fri, Mar 15, 2019 at 12:22:15AM +0100, Vincent Blut wrote:
> Hey Miroslav,
>
> Here is my work to make chronyd usuable on Debian 9 (current stable
On Fri, Mar 15, 2019 at 12:22:15AM +0100, Vincent Blut wrote:
Hey Miroslav,
Here is my work to make chronyd usuable on Debian 9 (current stable)
arm64 with the seccomp filter enabled.
Just tested on Debian unstable to check for any missing syscalls.
Seems good so far.
Cheers,
Vincent
From
On Thu, Mar 14, 2019 at 09:12:31AM +0100, Miroslav Lichvar wrote:
On Wed, Mar 13, 2019 at 06:10:20PM +0100, Vincent Blut wrote:
Hey,
I got a report that chronyd currently fails to start on Debian armel (ARM
EABI). Patch attached!
Applied, thanks. It looks like the seccomp support is now
Hey,
I got a report that chronyd currently fails to start on Debian armel
(ARM EABI). Patch attached!
Cheers,
Vincent
From b5b784dfce0a61bc26c34abcf8f0c86cba19da3e Mon Sep 17 00:00:00 2001
From: Leigh Brown
Date: Wed, 13 Mar 2019 17:56:08 +0100
Subject: [PATCH] sys_linux: allow recv and send
816e120580edba67eeb6ed92bd7d0775bb276a81 Mon Sep 17 00:00:00 2001
From: Vincent Blut
Date: Thu, 28 Feb 2019 16:43:56 +0100
Subject: [PATCH] sys_linux: allow waitpid in seccomp filter
---
sys_linux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys_linux.c b/sys_linux.c
index aee5a5e
Sep 17 00:00:00 2001
From: Vincent Blut
Date: Thu, 28 Feb 2019 14:39:13 +0100
Subject: [PATCH] sys_linux: allow _llseek in seccomp filter
This is needed on various 32-bit platforms to reposition read/write file
offset on {raw}measurements and statistics log files.
---
sys_linux.c | 8
1
On Mon, Sep 10, 2018 at 03:02:05PM +0200, Miroslav Lichvar wrote:
On Sat, Sep 08, 2018 at 02:04:49PM +0200, Vincent Blut wrote:
> Just wanted to let you know that this test makes chrony-3.4-pre1 FTBFS
> on HPPA.
>
>
https://buildd.debian.org/status/fetch.php?pkg=chrony=hppa=
On Wed, Sep 05, 2018 at 02:32:15PM +0200, Vincent Blut wrote:
Hey Miroslav,
On Fri, Aug 24, 2018 at 07:09:43PM +0200, g...@tuxfamily.net wrote:
commit 7889d108c288ab2de54aaad9ab9b9a5bfaca0a6c
Author: Miroslav Lichvar
Date: Thu Aug 23 17:06:50 2018 +0200
test: add samplefilt unit test
Hey Miroslav,
On Fri, Aug 24, 2018 at 07:09:43PM +0200, g...@tuxfamily.net wrote:
commit 7889d108c288ab2de54aaad9ab9b9a5bfaca0a6c
Author: Miroslav Lichvar
Date: Thu Aug 23 17:06:50 2018 +0200
test: add samplefilt unit test
Just wanted to let you know that this test makes
Hi,
SIGSYS is incorrectly spelled in the chronyd man page. The attached
patch fix that.
Cheers,
Vincent
From 5ff708195cf200e2f8ffac4b09b4c005424baeba Mon Sep 17 00:00:00 2001
From: Vincent Blut <vincent.deb...@free.fr>
Date: Thu, 30 Nov 2017 22:30:10 +0100
Subject: [PATCH] doc: fi
Hello,
While preparing chrony 3.2-pre2 for Debian, our tool lintian spotted a
spelling error in the chrony.conf man page. Patch attached!
Cheers,
Vincent
From 7e75ab0aa99ad1b6a23642015639dcf2724e1354 Mon Sep 17 00:00:00 2001
From: Vincent Blut <vincent.deb...@free.fr>
Date: Sun, 3 Sep 2
On Wed, Apr 26, 2017 at 03:43:58PM +0200, Miroslav Lichvar wrote:
On Wed, Apr 26, 2017 at 03:29:03PM +0200, Vincent Blut wrote:
>sys_linux: allow sysinfo in seccomp filter
>
>It may be used by glob() in latest glibc.
Do you have an idea about which commit in glibc justifies t
On Fri, Oct 21, 2016 at 04:35:55PM -0700, Bill Unruh wrote:
On Fri, 21 Oct 2016, Bill Unruh wrote:
On Sat, 22 Oct 2016, Rune Magnussen wrote:
Hi
When trying to install chrony from source, I found out that the README
refered to INSTALL which does not exist. Also asciidoctor is needed
during
On Wed, Sep 07, 2016 at 11:19:24AM +0200, Miroslav Lichvar wrote:
On Tue, Sep 06, 2016 at 12:40:08PM +0200, Miroslav Lichvar wrote:
When the system clock is adjusted, all dump files are immediately
invalid (even if they were not loaded), so we might want to remove all
*.dat files in the dumpdir
Hi Bill,
Sorry for the delay in answering, I’ve been absorbed by high priority
things and ended up forgetting about this thread.
On Sat, Aug 27, 2016 at 01:20:13PM -0700, Bill Unruh wrote:
On Sat, 27 Aug 2016, Vincent Blut wrote:
Hi,
Currently, the measurement history is persistent
Hi,
Currently, the measurement history is persistent for each sources no
matter if it is inspected by chronyd afterward. This persistence might
cause some staled measurements. Thus, I think it would be nice to have a
clean way (meaning not having to write a shell script ;-) ) to deal with
47 matches
Mail list logo
