head 1.2;
access;
symbols
RELENG_5_5_0_RELEASE:1.1.1.2.26.1
RELENG_5_5:1.1.1.2.26.1.0.6
RELENG_5_5_BP:1.1.1.2.26.1
RELENG_5_4_0_RELEASE:1.1.1.2.26.1
RELENG_5_4:1.1.1.2.26.1.0.4
RELENG_5_4_BP:1.1.1.2.26.1
RELENG_4_11_0_RELEASE:1.1.1.2
RELENG_4_11:1.1.1.2.0.28
RELENG_4_11_BP:1.1.1.2
RELENG_5_3_0_RELEASE:1.1.1.2.26.1
RELENG_5_3:1.1.1.2.26.1.0.2
RELENG_5_3_BP:1.1.1.2.26.1
RELENG_5:1.1.1.2.0.26
RELENG_5_BP:1.1.1.2
RELENG_4_10_0_RELEASE:1.1.1.2
RELENG_4_10:1.1.1.2.0.24
RELENG_4_10_BP:1.1.1.2
RELENG_5_2_1_RELEASE:1.1.1.2
RELENG_5_2_0_RELEASE:1.1.1.2
RELENG_5_2:1.1.1.2.0.22
RELENG_5_2_BP:1.1.1.2
v8_3_7:1.1.1.2
RELENG_4_9_0_RELEASE:1.1.1.2
RELENG_4_9:1.1.1.2.0.20
RELENG_4_9_BP:1.1.1.2
v8_3_6:1.1.1.2
RELENG_5_1_0_RELEASE:1.1.1.2
RELENG_5_1:1.1.1.2.0.18
RELENG_5_1_BP:1.1.1.2
RELENG_4_8_0_RELEASE:1.1.1.2
RELENG_4_8:1.1.1.2.0.16
RELENG_4_8_BP:1.1.1.2
v8_3_4:1.1.1.2
RELENG_5_0_0_RELEASE:1.1.1.2
RELENG_5_0:1.1.1.2.0.14
RELENG_5_0_BP:1.1.1.2
RELENG_4_7_0_RELEASE:1.1.1.2
RELENG_4_7:1.1.1.2.0.12
RELENG_4_7_BP:1.1.1.2
RELENG_4_6_2_RELEASE:1.1.1.2
RELENG_4_6_1_RELEASE:1.1.1.2
v8_3_3:1.1.1.2
RELENG_4_6_0_RELEASE:1.1.1.2
RELENG_4_6:1.1.1.2.0.10
RELENG_4_6_BP:1.1.1.2
v8_3_2_t1b:1.1.1.2
RELENG_4_5_0_RELEASE:1.1.1.2
RELENG_4_5:1.1.1.2.0.8
RELENG_4_5_BP:1.1.1.2
RELENG_4_4_0_RELEASE:1.1.1.2
RELENG_4_4:1.1.1.2.0.6
RELENG_4_4_BP:1.1.1.2
v8_2_4:1.1.1.2
RELENG_4_3_0_RELEASE:1.1.1.2
RELENG_4_3:1.1.1.2.0.4
RELENG_4_3_BP:1.1.1.2
v8_2_3:1.1.1.2
RELENG_4_2_0_RELEASE:1.1.1.2
v8_2_3_t6b:1.1.1.2
RELENG_4_1_1_RELEASE:1.1.1.2
PRE_SMPNG:1.1.1.2
RELENG_4_1_0_RELEASE:1.1.1.2
RELENG_3_5_0_RELEASE:1.1.1.1.2.1
RELENG_4_0_0_RELEASE:1.1.1.2
RELENG_4:1.1.1.2.0.2
RELENG_4_BP:1.1.1.2
RELENG_3_4_0_RELEASE:1.1.1.1.2.1
v8_2_2_p5:1.1.1.2
RELENG_3_3_0_RELEASE:1.1.1.1
RELENG_3_2_PAO:1.1.1.1.0.4
RELENG_3_2_PAO_BP:1.1.1.1
RELENG_3_2_0_RELEASE:1.1.1.1
RELENG_3_1_0_RELEASE:1.1.1.1
RELENG_3:1.1.1.1.0.2
RELENG_3_BP:1.1.1.1
RELENG_3_0_0_RELEASE:1.1.1.1
v8_1_2:1.1.1.1
bind_8_1_2_t3b:1.1.1.1
ISC:1.1.1;
locks; strict;
comment @# @;
1.2
date 2004.09.24.19.48.40; author des; state dead;
branches;
next 1.1;
1.1
date 98.05.03.04.11.31; author peter; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 98.05.03.04.11.31; author peter; state Exp;
branches
1.1.1.1.2.1;
next 1.1.1.2;
1.1.1.2
date 99.11.30.02.41.48; author peter; state Exp;
branches
1.1.1.2.26.1;
next ;
1.1.1.2.26.1
date 2004.09.26.03.09.22; author des; state dead;
branches;
next ;
1.1.1.1.2.1
date 99.12.13.15.05.38; author peter; state Exp;
branches;
next ;
desc
@@
1.2
log
@Retire the BIND 8 sources.
@
text
@
BIND key Statement
BIND Configuration File Guide--key Statement
Syntax
key key_id {
algorithm algorithm_id;
secret secret_string;
};
Definition and Usage
The key statement defines a key ID which can be used
in a server statement to
associate an authentication method with a particular name server.
A key ID must be created with the key
statement before it can be used in a server
definition.
The algorithm_id is a string that specifies a
security/authentication algorithm.
secret_string is the secret to be used by the algorithm.
The key statement is intended for future use by the
server. It is checked for syntax but is otherwise ignored.
[ BIND Config. File
| BIND Home
| ISC ]
Last Updated: $Id: key.html,v 1.5 1998/03/21 01:03:13 halley Exp $
@
1.1
log
@Initial revision
@
text
@@
1.1.1.1
log
@Import (trimmed) ISC bind-8.1.2-t3b. This will be updated to 8.1.2 on
final release.
Obtained from: ftp.isc.org
@
text
@@
1.1.1.1.2.1
log
@MFC: bind 8.2.2.p5
Urged by: imp, alfred, and a whole bunch of other folks.
Approved by: jkh (a few days ago)
@
text
@d26 1
a26 1
in a server statement to
d31 1
a31 1
definition or an address match list.
d34 2
a35 2
security/authentication algorithm. The only supported
algorithm is "hmac-md5".
d37 2
a38 9
secret_string is the secret to be used by the algorithm,
and is treated as a base-64 encoded string. This may be generated
using dnskeygen or another utility or created manually.
The key statement is intended for use in transaction
security. Unless included in a server
statement, it is not used to sign any requests. It is used to verify
requests matching the key_id and algorithm_id,
and sign replies to those requests.
d42 2
a43 2
| BIND Home
| ISC ]
d47 1
a47 1
Last Updated: $Id: key.html,v 1.10 1999/09/15 20:28:02 cyarnell Exp $
@
1.1.1.2
log
@Import bind v8.2.2.p5, minus the crypto for the time being. The bind
package does have BXA export approval, but the licensing strings on the
dnssafe code are a bit unpleasant. The crypto is easy to restore and bind
will run without it - just without full dnssec support.
Obtained from: The Internet Software Consortium (www.isc.org)
@
text
@d26 1
a26 1
in a server statement to
d31 1
a31 1
definition or an address match list.
d34 2
a35 2
security/authentication algorithm. The only supported
algorithm is "hmac-md5".
d37 2
a38 9
secret_string is the secret to be used by the algorithm,
and is treated as a base-64 encoded string. This may be generated
using dnskeygen or another utility or created manually.
The key statement is intended for use in transaction
security. Unless included in a server
statement, it is not used to sign any requests. It is used to verify
requests matching the key_id and algorithm_id,
and sign replies to those requests.
d42 2
a43 2
| BIND Home
| ISC ]
d47 1
a47 1
Last Updated: $Id: key.html,v 1.10 1999/09/15 20:28:02 cyarnell Exp $
@
1.1.1.2.26.1
log
@MFC: BIND 9 and related bits.
Approved by: re
@
text
@@