From 8fb0f1fa4253720a5da09f28c20696e4d666173c Mon Sep 17 00:00:00 2001 From: Brian Wellington Date: Tue, 29 Jan 2002 23:30:32 +0000 Subject: [PATCH] regen --- bin/nsupdate/nsupdate.8 | 19 +++++++++++++------ bin/nsupdate/nsupdate.html | 38 +++++++++++++++++++++++++++----------- 2 files changed, 40 insertions(+), 17 deletions(-) diff --git a/bin/nsupdate/nsupdate.8 b/bin/nsupdate/nsupdate.8 index 9d469db25b..86821680c0 100644 --- a/bin/nsupdate/nsupdate.8 +++ b/bin/nsupdate/nsupdate.8 @@ -52,10 +52,10 @@ made and the replies received from the name server. .PP Transaction signatures can be used to authenticate the Dynamic DNS updates. -These use the TSIG resource record type described in RFC2845. -The signatures rely on a shared secret that should only be known to -\fBnsupdate\fR -and the name server. +These use the TSIG resource record type described in RFC2845 or the +SIG(0) record described in RFC3535 and RFC2931. +TSIG relies on a shared secret that should only be known to +\fBnsupdate\fR and the name server. Currently, the only supported encryption algorithm for TSIG is HMAC-MD5, which is defined in RFC 2104. Once other algorithms are defined for TSIG, applications will need to @@ -70,6 +70,8 @@ statements would be added to so that the name server can associate the appropriate secret key and algorithm with the IP address of the 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. \fBnsupdate\fR does not read \fI/etc/named.conf\fR. @@ -79,8 +81,8 @@ uses the \fB-y\fR or \fB-k\fR -option to provide the shared secret needed to generate a TSIG record -for authenticating Dynamic DNS update requests. +option (with an HMAC-MD5 key) to provide the shared secret needed to generate +a TSIG record for authenticating Dynamic DNS update requests. These options are mutually exclusive. With the \fB-k\fR @@ -110,6 +112,10 @@ This may be visible in the output from \fBps\fR(1) or in a history file maintained by the user's shell. .PP +The \fB-k\fR 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. +.PP By default \fBnsupdate\fR uses UDP to send update requests to the name server. @@ -331,6 +337,7 @@ base-64 encoding of HMAC-MD5 key created by \fBRFC2845\fR, \fBRFC1034\fR, \fBRFC2535\fR, +\fBRFC2931\fR, \fBnamed\fR(8), \fBdnssec-keygen\fR(8). .SH "BUGS" diff --git a/bin/nsupdate/nsupdate.html b/bin/nsupdate/nsupdate.html index b8e63dcaea..03ac5db770 100644 --- a/bin/nsupdate/nsupdate.html +++ b/bin/nsupdate/nsupdate.html @@ -130,13 +130,13 @@ made and the replies received from the name server.

Transaction signatures can be used to authenticate the Dynamic DNS updates. -These use the TSIG resource record type described in RFC2845. -The signatures rely on a shared secret that should only be known to +These use the TSIG resource record type described in RFC2845 or the +SIG(0) record described in RFC3535 and RFC2931. +TSIG relies on a shared secret that should only be known to nsupdate -and the name server. +> and the name server. Currently, the only supported encryption algorithm for TSIG is HMAC-MD5, which is defined in RFC 2104. Once other algorithms are defined for TSIG, applications will need to @@ -160,6 +160,8 @@ CLASS="FILENAME" so that the name server can associate the appropriate secret key and algorithm with the IP address of the 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. nsupdate-k -option to provide the shared secret needed to generate a TSIG record -for authenticating Dynamic DNS update requests. +option (with an HMAC-MD5 key) to provide the shared secret needed to generate +a TSIG record for authenticating Dynamic DNS update requests. These options are mutually exclusive. With the or in a history file maintained by the user's shell.

The -k 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.

By default

INPUT FORMAT

EXAMPLES

FILES

SEE ALSO

RFC2931, +named(8), @@ -944,7 +960,7 @@ CLASS="REFENTRYTITLE" >

BUGS