[ntp:questions] FW: authenticated packet using alternate digest algorithms

Greg.Dowd at microchip.com Greg.Dowd at microchip.com
Mon Apr 29 14:44:50 UTC 2019

Hey, am I missing something here?  I'm looking at ntpd 4.2.6 and 4.2.8.  A customer pointed to the ntp.keys web page and asked about using sha512.  The link is
and it appears to clearly show how to use any digest algorithm supported by openssl.  When I create a keyfile and run ntpd in debug mode, sure enough they all get parsed and assigned a digest id for digest algorithms md5, sha1, ripemd160, sha224, 256,384 and 512.

Here are some keys:
6 MD5 zs"a@'r`&QiNW>ihD;YF  # MD5 key
7 MD5 qEU<XkWN-M]\$H~>|"F+  # MD5 key
8 MD5 ^TLS~EmRl}Jx~l$:^3o.  # MD5 key
9 MD5 'uL(75Gz_*S906yG$K_?  # MD5 key
10 MD5 ExZU8%k2h]`_S_cjLv+^  # MD5 key
11 SHA1 771fc6d1010f4e1d1fb4018de76d1c18826ccdea  # SHA1 key
12 SHA1 eac734f1acf1bf3556eb44aa2d6a71cc696009e2  # SHA1 key
13 SHA1 4a52b7c96900941dd84c2f3524a547db9dec2cb4  # SHA1 key
14 SHA1 ca6789d1a6623b61447e20aa4484a991b166f73c  # SHA1 key
15 SHA1 a685eb967977d90441486768f05cc6cb24581d98  # SHA1 key
16 SHA1 2a7d7e1b7e72d2083f3333575afaefc1945faa6b  # SHA1 key
17 SHA1 126fc66ec429e8002f0328990813c33f0e70f6a3  # SHA1 key
18 SHA1 287f749a2b4cd12535ae8d072f86edce9e28fa67  # SHA1 key
19 SHA1 2915015e44948758cf8a529513364fc5a852d320  

Greg Dowd
Principal Engineering Technologist, FTD
3870 N. First St. | San Jose | CA 95134 | USA
Office: 408.964.7643
Email: greg.dowd at microchip.com
Company Website:  www.microsemi.com

More information about the questions mailing list