<html lang='en'>
<head>
<meta content='text/html; charset=utf-8' http-equiv='Content-Type'>
<title>
GitLab
</title>
</meta>
</head>
<style>
img {
max-width: 100%;
height: auto;
}
p.details {
font-style:italic;
color:#777
}
.footer p {
font-size:small;
color:#777
}
pre.commit-message {
white-space: pre-wrap;
}
.file-stats a {
text-decoration: none;
}
.file-stats .new-file {
color: #090;
}
.file-stats .deleted-file {
color: #B00;
}
</style>
<body>
<div class='content'>
<h3>
Mark Atwood pushed to branch master
at <a href="https://gitlab.com/NTPsec/ntpsec">NTPsec / ntpsec</a>
</h3>
<h4>
Commits:
</h4>
<ul>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/172c9a7c4d07a9bb0dc054c1c37d68570280dcc8">172c9a7c</a></strong>
<div>
<span>by Sanjeev Gupta</span>
<i>at 2016-01-19T19:45:24+08:00</i>
</div>
<pre class='commit-message'>Correct references from keygen.html to ntpkeygen.html</pre>
</li>
<li>
<strong><a href="https://gitlab.com/NTPsec/ntpsec/commit/ca8d799b2ab28a442ee26bc9e8acb2e1a726b3a4">ca8d799b</a></strong>
<div>
<span>by Mark Atwood</span>
<i>at 2016-01-19T20:57:45+00:00</i>
</div>
<pre class='commit-message'>Merge branch 'LINKS' into 'master'
Correct references from keygen.html to ntpkeygen.html
See merge request !4</pre>
</li>
</ul>
<h4>3 changed files:</h4>
<ul>
<li class='file-stats'>
<a href='#diff-0'>
docs/authentic.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-1'>
docs/autokey.txt
</a>
</li>
<li class='file-stats'>
<a href='#diff-2'>
docs/debug.txt
</a>
</li>
</ul>
<h4>Changes:</h4>
<li id='diff-0'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/c296aa7a23dfd8079a2fe6531b9741437eaec5c0...ca8d799b2ab28a442ee26bc9e8acb2e1a726b3a4#diff-0'>
<strong>
docs/authentic.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/authentic.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/authentic.txt
</span><span style="color: #aaaaaa">@@ -345,7 +345,7 @@ routines required.
</span> //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
<span style="color: #000000;background-color: #ffdddd">-//program, or the link:keygen.html[+{ntpkeygen}+] utility program in the
</span><span style="color: #000000;background-color: #ddffdd">+//program, or the link:ntpkeygen.html[+{ntpkeygen}+] utility program in the
</span> //NTP software distribution.
Note that according to US law, NTP binaries including OpenSSL library
<span style="color: #aaaaaa">@@ -359,7 +359,7 @@ US.
</span> 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
<span style="color: #000000;background-color: #ffdddd">-link:keygen.html[{ntpkeygen}] page describes the files required for the
</span><span style="color: #000000;background-color: #ddffdd">+link:ntpkeygen.html[{ntpkeygen}] page describes the files required for the
</span> various authentication schemes. Further details are in the briefings,
papers and reports at the {project-shortname} project page linked from
{project-weblink}.
</code></pre>
<br>
</li>
<li id='diff-1'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/c296aa7a23dfd8079a2fe6531b9741437eaec5c0...ca8d799b2ab28a442ee26bc9e8acb2e1a726b3a4#diff-1'>
<strong>
docs/autokey.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/autokey.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/autokey.txt
</span><span style="color: #aaaaaa">@@ -88,7 +88,7 @@ symmetric key or public key cryptography.
</span>
Autokey uses industry standard X.509 public certificates, which can be
produced by commercial services, utility programs in the OpenSSL
<span style="color: #000000;background-color: #ffdddd">-software library, and the link:keygen.html[{ntpkeygen}] utility program
</span><span style="color: #000000;background-color: #ddffdd">+software library, and the link:ntpkeygen.html[{ntpkeygen}] utility program
</span> 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
<span style="color: #aaaaaa">@@ -454,7 +454,7 @@ digest schemes or identity schemes and must be corrected by installing
</span> 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
<span style="color: #000000;background-color: #ffdddd">-link:keygen.html[+{ntpkeygen}+ - generate public and private keys]
</span><span style="color: #000000;background-color: #ddffdd">+link:ntpkeygen.html[+{ntpkeygen}+ - generate public and private keys]
</span> program.
The following error codes are reported via the NTP control and
<span style="color: #aaaaaa">@@ -501,7 +501,7 @@ file if configured.
</span> [[files]]
== Files ==
<span style="color: #000000;background-color: #ffdddd">-See the link:keygen.html[+{ntpkeygen}+] page. Note that provisions to
</span><span style="color: #000000;background-color: #ddffdd">+See the link:ntpkeygen.html[+{ntpkeygen}+] page. Note that provisions to
</span> 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
</code></pre>
<br>
</li>
<li id='diff-2'>
<a href='https://gitlab.com/NTPsec/ntpsec/compare/c296aa7a23dfd8079a2fe6531b9741437eaec5c0...ca8d799b2ab28a442ee26bc9e8acb2e1a726b3a4#diff-2'>
<strong>
docs/debug.txt
</strong>
</a>
<hr>
<pre class="highlight"><code><span style="color: #000000;background-color: #ffdddd">--- a/docs/debug.txt
</span><span style="color: #000000;background-color: #ddffdd">+++ b/docs/debug.txt
</span><span style="color: #aaaaaa">@@ -201,7 +201,7 @@ cryptography servers and clients share session keys contained in a
</span> 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
<span style="color: #000000;background-color: #ffdddd">-required are produced by the link:keygen.html[+{ntpkeygen}+] program.
</span><span style="color: #000000;background-color: #ddffdd">+required are produced by the link:ntpkeygen.html[+{ntpkeygen}+] program.
</span>
Problems with symmetric key authentication are usually due to mismatched
keys or improper use of the +trustedkey+ command. A simple way to check
</code></pre>
<br>
</li>
</div>
<div class='footer' style='margin-top: 10px;'>
<p>
—
<br>
<a href="https://gitlab.com/NTPsec/ntpsec/compare/c296aa7a23dfd8079a2fe6531b9741437eaec5c0...ca8d799b2ab28a442ee26bc9e8acb2e1a726b3a4">View it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can
adjust your notification settings.
</p>
</div>
</body>
</html>