NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38.

ntp-4.2.8p13 was released on 07 March 2019. It addresses 1 medium-severity security issue in ntpd, and provides 17 non-security bugfixes and 1 other improvements over 4.2.8p12.

Please see the NTP Security Notice for vulnerability and mitigation details.

---

Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.

6.8. Autokey Configuration for NTP 4.2.4 (and earlier)

This topic provides a step-by-step guide for setting up NTP Autokey Authentication for NTP versions up through 4.2.4.

Users of NTP-4.2.6, or later, should consult Autokey Configuration for NTP 4.2.6

See the NTP Authentication specification and the Briefing Slides on the Network Time Synchronization Project page for in-depth information about NTP Authentication.

There are three Identity Schemes available in the NTP Reference Implemenation: IFF, GQ, and MV. See the Identity Scheme documentation for detailed information about the Identity Schemes. Although examples of server parameter generation and client parameter installation are provided for all available Identity Schemes, it is not necessary to use all of them.

Enforcement of NTP Authentication (with restrict statements) is beyond the scope of this topic

6.8.2.2.1. Broadcast and Multicast Autokey are configured on the server side. 6.8.3.2.1. Unicast Autokey is configured on the client side

Read 6.8.1. How To Use This Guide before starting

6.8.1. How To Use This Guide

1. Chose what type of Association you will be authenticating: Unicast, Multicast, or Broadcast
2. Choose the Idenity Scheme you will be using: IFF, GQ, or MV
3. Perform all of the steps for your chosen Association Type and Identity Scheme
4. Ignore the steps for other Association Types and Identity Schemes
5. Perform the server set-up before performing the client set-up

6.8.2. Server Set-Up

This section pertains only to systems that will be ntp servers for an NTP Trust Group; see 6.8.3. Client Set-Up for systems that will only be ntp clients. Trusted ntp servers which also operate as clients of other ntp servers may need to 6.8.3.4. Install Group/Client Keys.

6.8.2.1. Create the NTP Keys directory

Create a directory for the NTP Keys (e.g /etc/ntp.)

6.8.2.2. Edit ntp.conf

Add the following lines to ntp.conf:

crypto pw serverpassword
keysdir /etc/ntp

You may need to add the following line to ntp.conf if ntpd dies with a crypto_setup: random seed file not found error:

crypto randfile /dev/urandom

6.8.2.2.1. Broadcast and Multicast Autokey

Append autokey to the broadcast line in ntp.conf for the broadcast/multicast address that you want to authenticate with Autokey:

broadcast my.broadcast.or.multicast.address autokey

The assigned NTP Multicast address is 224.0.1.1, but other valid multicast addresses may be used.

6.8.2.3. Generate Server Parameters

This section covers Server Parameter generation for all Identity Schemes. You only need to generate the Server Parameters for the Identity Scheme(s) that you have chosen to use for your NTP Trust Group.

The server key and certificate will be generated if they are missing when a set of parameters are generated. The server certificate will be updated when existing parameters are updated or additional parameters are generated.

When you generate additional sets of parameters you must provide the serverpassword (as shown in 6.8.2.3.4. Multiple Identity Schemes) so that ntp-keygen can access the server key.

The -T option for ntp-keygen should only be used by a Trusted Authority (e.g time-server) for an NTP Trust Group.

6.8.2.3.1. IFF Parameters

The IFF parameter generation process produces a server key which should not be distributed to other members of the NTP Trust Group.

Generate the IFF parameters with the following commands:

cd /etc/ntp
ntp-keygen -T -I -p serverpassword

You must export an IFF Group Key for each client using that client's password. The client password is stored in the client ntp.conf in 6.8.3.2. Edit ntp.conf.

Export the IFF Group Key with the following commands:

cd /etc/ntp
ntp-keygen -e -q serverpassword -p clientpassword

The IFF Group Key will be directed to STDOUT unless you redirect it to a file. The target name of the IFF GRoup Key file is on one of the first lines of the output.

You can share a group password with all clients, use individual passwords for each client, or no password at all. This exported IFF Group Key will be used in 6.8.3.4.1. IFF Group Keys

IFF Group Keys may be distributed through a Web Form or even by pasting them across terminal windows.

IFF Group Keys may also be extracted and mailed with the following commands:

cd /etc/ntp
ntp-keygen -e -q serverpassword -p clientpassword | mail timelord@client.domain

6.8.2.3.2. GQ Parameters

The GQ parameter generation process produces a key file which is shared between all members of an NTP Trust Group.

You must use the same crypto password on all members of an NTP Trust Group for the GQ Identity Scheme.

Generate the GQ parameters with the following commands:

cd /etc/ntp
ntp-keygen -T -G -p serverpassword

6.8.2.3.3. MV Parameters

The MV parameter generation process produces a server key, which must not be distributed to other members of the NTP Trust Group, and a number of client keys which are used in 6.8.3.4.3. MV Client Keys

When choosing the number of client keys avoid factors of 512 and don't exceed 30.

Generate the IFF parameters with the following commands (N-1 keys will be generated):

cd /etc/ntp
ntp-keygen -V N -p serverpassword.

6.8.2.3.4. Multiple Identity Schemes

Multiple Identity Schemes may be used simultaneously. Use the -q serverpassword option so that ntp-keygen can access the server key when generating additional sets of parameters as shown in the following example:

cd /etc/ntp
ntp-keygen -T -I -q serverpassword
ntp-keygen -T -G -q serverpassword
ntp-keygen -V 5 -q serverpassword

6.8.2.4. Restart ntpd

Restart ntpd. Watch the output of ntpq -p to make sure that the server is able to start.

6.8.2.5. Server Parameter Update

The server key and certificate are valid only for one year and should be updated periodically (e.g. monthly) with the following command:

cd /etc/ntp
ntp-keygen -T -q `awk '/crypto pw/ { print $3 }' </etc/ntp.conf`

6.8.3. Client Set-Up

This section pertains only to systems that will be clients of an NTP Trust Group.

6.8.3.1. Create the NTP Keys directory

Create a directory for the NTP Keys (e.g. /etc/ntp.)

6.8.3.2. Edit ntp.conf

Add the following lines to ntp.conf:

crypto pw clientpassword
keysdir /etc/ntp

You may need to add the following line to ntp.conf if ntpd dies with a crypto_setup: random seed file not found error:

crypto randfile /dev/urandom

6.8.3.2.1. Unicast Autokey

Append autokey to the server line for the time-server that you want to authenticate with Autokey in a unicast association:

server ntp.i_have_the_key.for autokey

6.8.3.3. Generate Client Parameters

Do not use the -T option for ntp-keygen on systems that are only clients of an NTP Trust Group.

Generate the client key /certificate with the following commands:

cd /etc/ntp
ntp-keygen -H -p clientpassword

6.8.3.4. Install Group/Client Keys

This section covers the installation of Group/Client Keys for all Identity Schemes. You only need to install the Group/Client Keys used by the NTP Trust Group that this client will be joining.

Group/Client Keys, and their associated passwords, should be regarded as confidential and not disseminated to others.

6.8.3.4.1. IFF Group Keys

Obtain the IFF group key, exported in 6.8.2.3.1. IFF Parameters via a secure means (e.g. an SSL Web Form or encrypted e-mail), copy the key file to the keysdir, and create the standard sym-link:

cd /etc/ntp
ln -s ntpkey_IFFkey_server.3301264563 ntpkey_iff_server 

You must create an ntpkey_iff_client sym-link to activate IFF. You may set this sym-link to point to any file in the keysdir. Such as:

ln -s ntpkey_host_client ntpkey_iff_client

6.8.3.4.2. GQ Group Keys

Obtain the GQ group key, generated in 6.8.2.3.2. GQ Parameters via a secure means, copy the key file to the keysdir, and create the standard sym-link:

cd /etc/ntp
ln -s ntpkey_GQpar_server.3301145293 ntpkey_gq_server

You must use the same crypto password on all members of an NTP Trust Group for the GQ Identity Scheme.

6.8.3.4.3. MV Client Keys

Obtain the MV client key, generated in 6.8.2.3.3. MV Parameters, via a secure means, copy the key file to the keysdir, and create the standard sym-link:

cd /etc/ntp
ln -s ntpkey_MVkey1_server.3301144193 ntpkey_mv_server

6.8.3.5. Restart ntpd

Restart ntpd. Watch the output of ntpq -p to make sure that the client is able to start and sync with the server.

6.8.3.6. Client Parameter Update

The client key and certificate are valid only for one year and should be updated periodically (e.g. monthly) with the following command:

cd /etc/ntp
ntp-keygen -q `awk '/crypto pw/ { print $3 }' </etc/ntp.conf`

6.8.4. Monitoring Authentication Status

It is not usually necessary to run ntpd in debug mode to troubleshoot Authentication problems.

Use ntpq -c "rv 0 cert" to view the Autokey certificates held by ntpd.

Use ntpq -c as to the check the authentication status of NTP associations. Authenticated associations display ok in the auth column:

ind assID status  conf reach auth condition  last_event cnt
===========================================================
  1 26132  f694   yes   yes   ok   sys.peer   reachable  9

For detailed information about an authenticated association use the assID from ntpq -cas in the following command:

ntpq -c"rv assID flags"

A fully functioning Autokey+IFF assocition will show the following flags on the client:

flags=0x83f21

6.8.4.1. Crypto Association Flags

/*
 * The following bits are set by the CRYPTO_ASSOC message from
 * the server and are not modified by the client.
 */
#define CRYPTO_FLAG_ENAB  0x0001 /* crypto enable */
#define CRYPTO_FLAG_TAI   0x0002 /* leapseconds table */

#define CRYPTO_FLAG_PRIV  0x0010 /* PC identity scheme */
#define CRYPTO_FLAG_IFF   0x0020 /* IFF identity scheme */
#define CRYPTO_FLAG_GQ    0x0040 /* GQ identity scheme */
#define CRYPTO_FLAG_MV    0x0080 /* MV identity scheme */
#define CRYPTO_FLAG_MASK  0x00f0 /* identity scheme mask */
        
/*
 * The following bits are used by the client during the protocol
 * exchange.
 */
#define CRYPTO_FLAG_VALID 0x0100 /* public key verified */
#define CRYPTO_FLAG_VRFY  0x0200 /* identity verified */
#define CRYPTO_FLAG_PROV  0x0400 /* signature verified */
#define CRYPTO_FLAG_AGREE 0x0800 /* cookie verifed */
#define CRYPTO_FLAG_AUTO  0x1000 /* autokey verified */
#define CRYPTO_FLAG_SIGN  0x2000 /* certificate signed */
#define CRYPTO_FLAG_LEAP  0x4000 /* leapseconds table verified */

6.8.5. Related Links

• Autokey Helper Script