File: chrony.keys.example

package info (click to toggle)
chrony 1.24-3%2Bsqueeze3
  • links: PTS
  • area: main
  • in suites: squeeze-lts
  • size: 2,640 kB
  • ctags: 2,657
  • sloc: ansic: 17,290; yacc: 871; sh: 758; perl: 426; makefile: 155
file content (27 lines) | stat: -rw-r--r-- 1,169 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
#######################################################################
# $Header: /cvs/src/chrony/examples/chrony.keys.example,v 1.1 2002/01/31 00:00:08 richard Exp $
#
# This is an example chrony keys file.  You should copy it to /etc/chrony.keys
# after editing it to set up the key(s) you want to use.  In most situations,
# you will require a single key (the 'commandkey') so that you can supply a
# password to chronyc to enable you to modify chronyd's operation whilst it is
# running.
#
# Copyright 2002 Richard P. Curnow
#
#######################################################################
# A valid key line looks like this

1 a_key

# It must consist of an integer, followed by whitespace, followed by a block of
# text with no spaces in it.  (You cannot put a space in a key).  If you wanted
# to use the above line as your commandkey (i.e. chronyc password), you would
# put the following line into chrony.conf (remove the # from the start):

# commandkey 1

# You might want to define more keys if you use the MD5 authentication facility
# in the network time protocol to authenticate request/response packets between
# trusted clients and servers.