[Git][NTPsec/ntpsec][master] 2 commits: Correct references from keygen.html to ntpkeygen.html

Mark Atwood gitlab at mg.gitlab.com
Tue Jan 19 20:57:54 UTC 2016


Mark Atwood pushed to branch master at NTPsec / ntpsec


Commits:
172c9a7c by Sanjeev Gupta at 2016-01-19T19:45:24+08:00
Correct references from keygen.html to ntpkeygen.html

- - - - -
ca8d799b by Mark Atwood at 2016-01-19T20:57:45+00:00
Merge branch 'LINKS' into 'master'

Correct references from keygen.html to ntpkeygen.html



See merge request !4
- - - - -


3 changed files:

- docs/authentic.txt
- docs/autokey.txt
- docs/debug.txt


Changes:

=====================================
docs/authentic.txt
=====================================
--- a/docs/authentic.txt
+++ b/docs/authentic.txt
@@ -345,7 +345,7 @@ routines required.
 //public values which are generated by each participant and where the
 //private value is never revealed. Autokey uses X.509 public certificates,
 //which can be produced by commercial services, the OpenSSL application
-//program, or the link:keygen.html[+{ntpkeygen}+] utility program in the
+//program, or the link:ntpkeygen.html[+{ntpkeygen}+] utility program in the
 //NTP software distribution.
 
 Note that according to US law, NTP binaries including OpenSSL library
@@ -359,7 +359,7 @@ US.
 Authentication is configured separately for each association using the
 +key+ or +autokey+ option of the +server+ configuration command, as
 described in the link:confopt.html[Server Options] page. The
-link:keygen.html[{ntpkeygen}] page describes the files required for the
+link:ntpkeygen.html[{ntpkeygen}] page describes the files required for the
 various authentication schemes. Further details are in the briefings,
 papers and reports at the {project-shortname} project page linked from
 {project-weblink}.


=====================================
docs/autokey.txt
=====================================
--- a/docs/autokey.txt
+++ b/docs/autokey.txt
@@ -88,7 +88,7 @@ symmetric key or public key cryptography.
 
 Autokey uses industry standard X.509 public certificates, which can be
 produced by commercial services, utility programs in the OpenSSL
-software library, and the link:keygen.html[{ntpkeygen}] utility program
+software library, and the link:ntpkeygen.html[{ntpkeygen}] utility program
 in the NTP software distribution. A certificate includes the subject
 name of the client, the issuer name of the server, the public key of the
 client and the time period over which the public and private keys
@@ -454,7 +454,7 @@ digest schemes or identity schemes and must be corrected by installing
 the correct media and/or correcting the configuration file. One of the
 most common errors is expired certificates, which must be regenerated
 and signed at least once per year using the
-link:keygen.html[+{ntpkeygen}+ - generate public and private keys]
+link:ntpkeygen.html[+{ntpkeygen}+ - generate public and private keys]
 program.
 
 The following error codes are reported via the NTP control and
@@ -501,7 +501,7 @@ file if configured.
 [[files]]
 == Files ==
 
-See the link:keygen.html[+{ntpkeygen}+] page. Note that provisions to
+See the link:ntpkeygen.html[+{ntpkeygen}+] page. Note that provisions to
 load leap second values from the NIST files have been removed. These
 provisions are now available whether or not the OpenSSL library is
 available. However, the functions that can download these values from


=====================================
docs/debug.txt
=====================================
--- a/docs/debug.txt
+++ b/docs/debug.txt
@@ -201,7 +201,7 @@ cryptography servers and clients share session keys contained in a
 secret key file In public key cryptography, which requires the OpenSSL
 software library, the server has a private key, never shared, and a
 public key with unrestricted distribution. The cryptographic media
-required are produced by the link:keygen.html[+{ntpkeygen}+] program.
+required are produced by the link:ntpkeygen.html[+{ntpkeygen}+] program.
 
 Problems with symmetric key authentication are usually due to mismatched
 keys or improper use of the +trustedkey+ command. A simple way to check



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/c296aa7a23dfd8079a2fe6531b9741437eaec5c0...ca8d799b2ab28a442ee26bc9e8acb2e1a726b3a4
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/vc/attachments/20160119/3495b8d1/attachment.html>


More information about the vc mailing list