mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-09-03 08:05:21 +00:00
Code Issues Releases Wiki Activity

document SIG(0) support.

Browse Source
This commit is contained in:
Brian Wellington
2002-01-29 23:30:12 +00:00
parent f5cb884c84
commit a20b2c5f53
1 changed files with 17 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
bin/nsupdate/nsupdate.docbook
View File

@@ -16,7 +16,7 @@
- WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. - WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
--> -->
<!-- $Id: nsupdate.docbook,v 1.9 2001/11/27 18:55:20 gson Exp $ --> <!-- $Id: nsupdate.docbook,v 1.10 2002/01/29 23:30:12 bwelling Exp $ -->
<refentry> <refentry>
<refentryinfo> <refentryinfo>
@@ -81,10 +81,10 @@ made and the replies received from the name server.
<para> <para>
Transaction signatures can be used to authenticate the Dynamic DNS Transaction signatures can be used to authenticate the Dynamic DNS
updates. updates.
These use the TSIG resource record type described in RFC2845. These use the TSIG resource record type described in RFC2845 or the
The signatures rely on a shared secret that should only be known to SIG(0) record described in RFC3535 and RFC2931.
<command>nsupdate</command> TSIG relies on a shared secret that should only be known to
and the name server. <command>nsupdate</command> and the name server.
Currently, the only supported encryption algorithm for TSIG is Currently, the only supported encryption algorithm for TSIG is
HMAC-MD5, which is defined in RFC 2104. HMAC-MD5, which is defined in RFC 2104.
Once other algorithms are defined for TSIG, applications will need to Once other algorithms are defined for TSIG, applications will need to
@@ -99,6 +99,8 @@ statements would be added to
so that the name server can associate the appropriate secret key so that the name server can associate the appropriate secret key
and algorithm with the IP address of the and algorithm with the IP address of the
client application that will be using TSIG authentication. client application that will be using TSIG authentication.
SIG(0) uses public key cryptography. To use a SIG(0) key, the public
key must be stored in a KEY record in a zone served by the name server.
<command>nsupdate</command> <command>nsupdate</command>
does not read does not read
<filename>/etc/named.conf</filename>. <filename>/etc/named.conf</filename>.
@@ -109,8 +111,8 @@ uses the
<option>-y</option> <option>-y</option>
or or
<option>-k</option> <option>-k</option>
option to provide the shared secret needed to generate a TSIG record option (with an HMAC-MD5 key) to provide the shared secret needed to generate
for authenticating Dynamic DNS update requests. a TSIG record for authenticating Dynamic DNS update requests.
These options are mutually exclusive. These options are mutually exclusive.
With the With the
<option>-k</option> <option>-k</option>
@@ -144,6 +146,11 @@ This may be visible in the output from
or in a history file maintained by the user's shell. or in a history file maintained by the user's shell.
</para> </para>
<para> <para>
The <option>-k</option> may also be used to specify a SIG(0) key used
to authenticate Dynamic DNS update requests. In this case, the key
specified is not an HMAC-MD5 key.
</para>
<para>
By default By default
<command>nsupdate</command> <command>nsupdate</command>
uses UDP to send update requests to the name server. uses UDP to send update requests to the name server.
@@ -537,6 +544,9 @@ base-64 encoding of HMAC-MD5 key created by
<refentrytitle>RFC2535</refentrytitle> <refentrytitle>RFC2535</refentrytitle>
</citerefentry>, </citerefentry>,
<citerefentry> <citerefentry>
<refentrytitle>RFC2931</refentrytitle>
</citerefentry>,
<citerefentry>
<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum> <refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>
</citerefentry>, </citerefentry>,
<citerefentry> <citerefentry>