| Re: [chrony-users] Obfusticated data? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Obfusticated data?
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 3 Oct 2022 09:07:22 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664780844; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4jilGqVxgPzyrXepyb+ghWvg2Xmp0uLL6SYhp2wn9DM=; b=cRDCeDtlGnwsW4FMsZgOkwEZpBAwBncra3ZYsUz0fABNYmYyQXIXD5xzOcbixrNn8co7zY +r9kPEtD8ZxvuKkpegiPeSH05e30jLOXj7yH3jl6zUVgrzmFt8fc6CwQvNIPeicHIvHNpO oyEkx8EHS73DhubgFWjaYer8YyrssPQ=
On Fri, Sep 30, 2022 at 08:33:01PM +0000, Mark Notarus wrote:
> We have been doing that by parsing local logs, which works fine but scales terribly.
What is the issue with scaling? You can could be polling the tracking
report, or pushing it from the client to a central location.
> Could someone help me understand the goal of this data deletion?
Here is a draft that described this idea:
https://datatracker.ietf.org/doc/html/draft-ietf-ntp-data-minimization-04
As a workaround, you can use specify the server as "peer" instead of
"server", which will disable the data minimization.
--
Miroslav Lichvar
--
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.