| RE: [chrony-users] Seeking assistance deciphering NTP packet capture |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-users] Seeking assistance deciphering NTP packet capture
- From: Bryan Evenson <bevenson@xxxxxxxxxxxxxx>
- Date: Mon, 6 Jun 2022 12:46:19 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=melinkcorp.com; dmarc=pass action=none header.from=melinkcorp.com; dkim=pass header.d=melinkcorp.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ilTirVThw2ApUdu8GJdAF2hJYWwdnDIwQm2YgsXMaoI=; b=jxoN6PwKXexJGl0kcsR20JwPovuXPdgtgvSOp7ptdKnDzIjzqAi95VLHXKx+p9xqD859FcfqtxFUd5/g2PR8Ihv/JDDw07qQkuO5sm7E9hTFfxbkfK5Thwj5Zg5sOApFkr8uLruEAZhEOvfAfHxQIAegBQ9lPHXcz7VWRj0rSTJqovyDJgG5Rw7x+DIllvqTtKqEzejJ4MOcJkE3XPzFtoaTt+a7Cvx76MSZILbgFxm/0+Qa3qJ/k8FvzVQzqzGczXiP1g3vYWT8ch7fmeGL2kHLk52KadEgDLjvxfNPyzTCEOk3UejBDeTBuIWJ5gMf+0RB+nhiw9JhBpuEmktnXQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=K3L0vsJ8euwVJVmkXAWfk2cnpY/5s8H3gOmhwmtRppdUaZ2Z0tFohdNE4GZsjhf2JuXuZ739OnhpchxHsc6RfAAjl4pzC8J8ncgXBJDIitu94mCt/kchLe5oG81v//vy3f9YoHyFfLvU8HzHl7hkSqBSeP3VmkfkjByd485bOgQmsbf7VGMFClIhh5cqNpGevu348U1U2/4y9Y/PTyfpT7Enz/XS1XiyLUolOoAH9AuHl7J98Qz8Vt2qm9xnLfke7PWokebGCOiIA0v91CjNEEip6Xu0RFnsuJifbnvz323yJSF7LG0xX+YiFXF8lHG1vdYluCSS261vseNh7dbfMQ==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=melinkcorp.com;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Melink.onmicrosoft.com; s=selector1-Melink-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ilTirVThw2ApUdu8GJdAF2hJYWwdnDIwQm2YgsXMaoI=; b=WF1RG9TqNYm+dhaey4JtiRXRYBnVaVMDNVY7Qv3XNju8/r4KGpYMer6ijMszhYxeTJgXpgJCoo1+QHZ+FXE0DwTNoaa1GtYlB9IE5XbYjaMYl2LT89dZdb/QVFTszIk4bZp0F1AjbBViB5Eu8fWAR3muJoGLNHa8n4TvUPy5VxVH2qeKgLUa6+DjuxgHybpRgviweHSLErC5sd1l9FUxv2KzvlxMSlzaxxeMqSyhaQCuRuhxPiSk/AL6JBNaaJzDwML5+ZOucLJ+yAU7oDhldZWc7DIMYYPQNYfkqbOr/GPjsgUkqlV7GtgmFt2ZVKkPcet6KoLvHQnN4MlfZgt2wg==
- Thread-index: Adh3fERlfGtrKcSjTpKGh0pE5vUnvQB/9XOAAAnHqjA=
- Thread-topic: [chrony-users] Seeking assistance deciphering NTP packet capture
Miroslav,
> -----Original Message-----
> From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
> Sent: Monday, June 6, 2022 4:05 AM
> To: chrony-users@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [chrony-users] Seeking assistance deciphering NTP packet
> capture
>
> On Fri, Jun 03, 2022 at 07:43:07PM +0000, Bryan Evenson wrote:
> > March 20, 1985 7:17:35 UTC
> > July 31, 2036 00:19:20 UTC
> > July 25, 2004, 05:41:48 UTC
> > Feb 16, 2061 19:03:36 UTC
> >
> > These were from packets send about one minute apart from each other.
> On the server response, the Reference Timestamp, Receive Timestamp and
> the Transmit Timestamp were all reasonably close to each other and were
> based on current time.
> >
> > Does someone know why the transmit timestamps are so far off from
> actual time? Is this just a data translation problem where Wireshark is
> reading the field format incorrectly?
>
> The client's transmit timestamps are completely random. The server doesn't
> need to know client's time. It's indicated by the precision of
> 32 in the packet. It's a security and privacy feature described here:
>
> https://datatracker.ietf.org/doc/html/draft-ietf-ntp-data-minimization-04
Thanks for the information. That makes sense. I'm going to be suggesting some modifications to the automated test kit to account for this.
Thanks,
Bryan Evenson
>
> --
> 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.
--
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.