Lines Matching full:keys

39 It can generate message digest keys used in symmetric key cryptography and,
40 if the OpenSSL software library has been installed, it can generate host keys,
41 signing keys, certificates, and identity keys and parameters used in Autokey
49 The message digest symmetric keys file is generated in a format
58 When used to generate message digest symmetric keys, the program
65 The message digest symmetric keys file must be distributed and stored
67 Besides the keys used for ordinary NTP associations, additional keys
81 However, the identity keys are probably not compatible with anything
127 The symmetric keys file, normally called
128 \fIntp.keys\f[],
163 \f\*[I-Font]keys\f[]
172 \f\*[I-Font]keys\f[]
188 existing keys and parameters and generates a new certificate file with
216 sign keys;
223 sign keys.
254 Installing the keys as root might not work in NFS-mounted
256 to the shared keys directory, even as root.
264 There is no need for one client to read the keys and certificates
282 All files are installed by default in the keys directory
286 The actual location of the keys directory
449 On each trusted host as root, change to the keys directory.
456 to generate keys and a trusted certificate.
459 flag to generate keys and nontrusted certificates.
501 using existing keys, and soft links.
532 In some schemes there are separate keys for servers and clients.
537 both server and client keys.
539 only as clients have key files that contain only client keys.
565 either the keys or certificates without copying them
574 scheme to generate keys
586 which includes both server and client keys.
596 of keys and certificates, these files can be refreshed as needed.
602 To eliminate this threat, the client keys can be extracted
612 To further protect the integrity of the keys,
621 scheme to generate keys
633 which includes both server and client keys.
649 at the same time, keys and certificates can be regenerated as needed.
657 scheme to generate keys
667 is the number of revokable keys (typically 5) to produce
692 scheme is independent of keys and certificates,
697 Set the number of bits in the identity modulus for generating identity keys to
731 Select the OpenSSL cipher to encrypt the files containing private keys.
754 client keys file previously specified
820 Generate a new symmetric keys file containing 10
822 keys, and if OpenSSL is available, 10
824 keys.
902 encrypted server keys and parameters for the Mu-Varadharajan (MV)
1011 The format of the symmetric keys file, ordinarily named
1012 \fIntp.keys\f[],
1049 Figure 1 shows a typical symmetric keys file used by the reference
1051 Following the header the keys are entered one per line in the format
1088 Note that the keys used by the
1094 and entered by hand, so it is generally appropriate to specify these keys
1101 program generates a symmetric keys file
1103 Since the file contains private shared keys,
1107 \fIntp.keys\f[],
1153 private keys.  The default is three-key triple DES in CBC mode,
1169 Write IFF or GQ identity keys.
1171 Write the public parameters from the IFF or GQ client keys to
1176 Generate GQ parameters and keys.
1178 Generate parameters and keys for the GQ identification scheme,
1184 Generate new host keys, obsoleting any that may exist.
1227 generate symmetric keys.
1229 Generate symmetric keys, obsoleting any that may exist.
1247 export IFF or GQ group keys with password.
1249 Export IFF or GQ identity group keys to the standard output,
1286 Generate parameters and keys for the Mu-Varadharajan (MV)
1289 .NOP \f\*[B-Font]\-v\f[] \f\*[I-Font]num\f[], \f\*[B-Font]\-\-mv\-keys\f[]=\f\*[I-Font]num\f[]
1290 update <num> MV keys.