Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ntp.keys(5) [freebsd man page]

NTP.KEYS(5)						      BSD File Formats Manual						       NTP.KEYS(5)

NAME
ntp.keys -- NTP daemon key file format SYNOPSIS
/etc/ntp.keys DESCRIPTION
Following is a description of the format of NTP key files. For a description of the use of these files, see the "Authentication Support" section of the ntp.conf(5) page. In the case of DES, the keys are 56 bits long with, depending on type, a parity check on each byte. In the case of MD5, the keys are 64 bits (8 bytes). ntpd(8) reads its keys from a file specified using the -k command line option or the keys statement in the configuration file. While key number 0 is fixed by the NTP standard (as 56 zero bits) and may not be changed, one or more of the keys numbered 1 through 15 may be arbitrarily set in the keys file. The key file uses the same comment conventions as the configuration file. Key entries use a fixed format of the form keyno type key where keyno is a positive integer, type is a single character which defines the key format, and key is the key itself. The key may be given in one of four different formats, controlled by the type character. The four key types, and corresponding formats, are listed following. S The key is a 64-bit hexadecimal number in the format specified in the DES specification; that is, the high order seven bits of each octet are used to form the 56-bit key while the low order bit of each octet is given a value such that odd parity is maintained for the octet. Leading zeroes must be specified (i.e., the key must be exactly 16 hex digits long) and odd parity must be maintained. Hence a zero key, in standard format, would be given as '0101010101010101'. N The key is a 64-bit hexadecimal number in the format specified in the NTP standard. This is the same as the DES format, except the bits in each octet have been rotated one bit right so that the parity bit is now the high order bit of the octet. Leading zeroes must be spec- ified and odd parity must be maintained. A zero key in NTP format would be specified as '8080808080808080'. A The key is a 1-to-8 character ASCII string. A key is formed from this by using the low order 7 bits of each ASCII character in the string, with zeroes added on the right when necessary to form a full width 56-bit key, in the same way that encryption keys are formed from UNIX passwords. M The key is a 1-to-8 character ASCII string, using the MD5 authentication scheme. Note that both the keys and the authentication schemes (DES or MD5) must be identical between a set of peers sharing the same key number. Note that the keys used by the ntpq(8) and ntpdc(8) programs are checked against passwords requested by the programs and entered by hand, so it is generally appropriate to specify these keys in ASCII format. FILES
/etc/ntp.keys the default name of the configuration file SEE ALSO
ntp.conf(5), ntpd(8), ntpdate(8), ntpdc(8) BUGS
ntpd(8) has gotten rather fat. While not huge, it has gotten larger than might be desirable for an elevated-priority daemon running on a workstation, particularly since many of the fancy features which consume the space were designed more with a busy primary server, rather than a high stratum workstation, in mind. BSD
January 13, 2000 BSD

Check Out this Related Man Page

ntp.keys(5)							   File Formats 						       ntp.keys(5)

NAME
ntp.keys - NTP symmetric key file format configuration file SYNOPSIS
[--option-name] [--option-name value] All arguments must be options. DESCRIPTION
This document describes the format of an NTP symmetric key file. For a description of the use of this type of file, see the "Authentica- tion Support" section of the ntp.conf(5) page. ntpd(8) reads its keys from a file specified using the -k command line option or the keys statement in the configuration file. While key number 0 is fixed by the NTP standard (as 56 zero bits) and may not be changed, one or more keys numbered between 1 and 65535 may be arbi- trarily set in the keys file. The key file uses the same comment conventions as the configuration file. Key entries use a fixed format of the form keyno type key opt_IP_list where keyno is a positive integer (between 1 and 65535), type is the message digest algorithm, key is the key itself, and opt_IP_list is an optional comma-separated list of IPs where the keyno should be trusted. that are allowed to serve time. Each IP in opt_IP_list may con- tain an optional /subnetbits specification which identifies the number of bits for the desired subnet of trust. If opt_IP_list is empty, any properly-authenticated message will be accepted. The key may be given in a format controlled by the type field. The type MD5 is always supported. If ntpd was built with the OpenSSL library then any digest library supported by that library may be specified. However, if compliance with FIPS 140-2 is required the type must be either SHA or SHA1. What follows are some key types, and corresponding formats: MD5 The key is 1 to 16 printable characters terminated by an EOL, whitespace, or a # (which is the "start of comment" character). SHA SHA1 RMD160 The key is a hex-encoded ASCII string of 40 characters, which is truncated as necessary. Note that the keys used by the ntpq(8) and ntpdc(8) programs are checked against passwords requested by the programs and entered by hand, so it is generally appropriate to specify these keys in ASCII format. FILES
/etc/ntp.keys the default name of the configuration file SEE ALSO
ntp.conf(5), ntpd(1), ntpdate(1), ntpdc(1), sntp(1) AUTHORS
The University of Delaware and Network Time Foundation COPYRIGHT
Copyright (C) 1992-2017 The University of Delaware and Network Time Foundation all rights reserved. This program is released under the terms of the NTP license, <http://ntp.org/license>. BUGS
Please send bug reports to: http://bugs.ntp.org, bugs@ntp.org NOTES
This document was derived from FreeBSD. This manual page was AutoGen-erated from the ntp.keys option definitions. 4.2.8p13 20 Feb 2019 ntp.keys(5)
Man Page