Olegandr

Capture uploaded [issues2999.pcap.gz](https://github.com/secdev/scapy/files/5646626/issues2999.pcap.gz)

No it is definitely not autokey. See linked issue.

Maybe this one https://www.rfc-editor.org/errata/eid3627 ? I mean those packets are created by widely-used NTP server/client implementations, are being parsed correctly by Wireshark. And no, this is not Autokey.

Looks like the project is mostly dead and not supported. Were you able to run at least anything? I tied but failed, it looks like I need to take outdated...

I just followed universal rules. Am I wrong? I could not found any install instructions to be frank.

I try to run test scrypts as per usage.md instructions and not able to do that, "fail to import from tlsfuzzer" What is the correct way for running it then?

US government standard requires that NTP be authenticated using " SHA1, SHA256, SHA384, SHA512, AES-CBC-128, AES-CBC-256 as the message digest algorithm(s)". That is why support for those fields are requested.

@guedou, Here is a capture with all possible digests: [alldigests2.zip](https://github.com/secdev/scapy/files/10388535/alldigests2.zip) Packets 1,2 SHA1 Packets 3,4 SHA256 Packets 5,6 SHA512 Packets7,8 SHA384, Packet 9 AES-CMAC 128 Packet 10 AES_CMAC 256 Sorry...

I was using chrony 4. afaik ntpd does not support AES-MAC.

was able to start wiht it, but not clear is this working at all --2019-02-02 16:36:21-- (try: 3) http://127.0.0.1:8888/stats Connecting to 127.0.0.1:8888... connected. HTTP request sent, awaiting response... Read error...