summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDarren Tucker <dtucker@zip.com.au>2003-10-15 16:07:53 +1000
committerDarren Tucker <dtucker@zip.com.au>2003-10-15 16:07:53 +1000
commit64b77bcb4b40c97eb1da058ee5648da1a34c3b63 (patch)
treed31b93369158d8d6ae1bca321f4ea93ac10074b7
parentdda19d63ffeed569c57f4b9359bc358abe690d23 (diff)
- jakob@cvs.openbsd.org 2003/10/14 19:43:23
[README.dns] update Resynced with OpenBSD too: DNSFP support is now always compiled in so the configure support (and documentation thereof) can go away.
-rw-r--r--ChangeLog5
-rw-r--r--README.dns23
2 files changed, 13 insertions, 15 deletions
diff --git a/ChangeLog b/ChangeLog
index 414a51f25..5d0201a71 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -33,6 +33,9 @@
33 - jakob@cvs.openbsd.org 2003/10/14 19:42:10 33 - jakob@cvs.openbsd.org 2003/10/14 19:42:10
34 [dns.c dns.h readconf.c ssh-keygen.c sshconnect.c] 34 [dns.c dns.h readconf.c ssh-keygen.c sshconnect.c]
35 include SSHFP lookup code (not enabled by default). ok markus@ 35 include SSHFP lookup code (not enabled by default). ok markus@
36 - jakob@cvs.openbsd.org 2003/10/14 19:43:23
37 [README.dns]
38 update
36 39
3720031009 4020031009
38 - (dtucker) [sshd_config.5] UsePAM defaults to "no". ok djm@ 41 - (dtucker) [sshd_config.5] UsePAM defaults to "no". ok djm@
@@ -1350,4 +1353,4 @@
1350 - Fix sshd BindAddress and -b options for systems using fake-getaddrinfo. 1353 - Fix sshd BindAddress and -b options for systems using fake-getaddrinfo.
1351 Report from murple@murple.net, diagnosis from dtucker@zip.com.au 1354 Report from murple@murple.net, diagnosis from dtucker@zip.com.au
1352 1355
1353$Id: ChangeLog,v 1.3077 2003/10/15 06:00:47 dtucker Exp $ 1356$Id: ChangeLog,v 1.3078 2003/10/15 06:07:53 dtucker Exp $
diff --git a/README.dns b/README.dns
index e24092e03..97879183e 100644
--- a/README.dns
+++ b/README.dns
@@ -1,17 +1,13 @@
1How to verify host keys using OpenSSH and DNS 1How to verify host keys using OpenSSH and DNS
2--------------------------------------------- 2---------------------------------------------
3 3
4OpenSSH contains experimental support for verifying host keys using DNS 4OpenSSH contains support for verifying host keys using DNS as described in
5as described in draft-ietf-secsh-dns-xx.txt. The document contains 5draft-ietf-secsh-dns-05.txt. The document contains very brief instructions
6very brief instructions on how to test this feature. Configuring DNS 6on how to use this feature. Configuring DNS is out of the scope of this
7and DNSSEC is out of the scope of this document. 7document.
8 8
9 9
10(1) Enable DNS fingerprint support in OpenSSH 10(1) Server: Generate and publish the DNS RR
11
12 configure --with-dns
13
14(2) Generate and publish the DNS RR
15 11
16To create a DNS resource record (RR) containing a fingerprint of the 12To create a DNS resource record (RR) containing a fingerprint of the
17public host key, use the following command: 13public host key, use the following command:
@@ -24,15 +20,14 @@ you should generate one RR for each key.
24 20
25In the example above, ssh-keygen will print the fingerprint in a 21In the example above, ssh-keygen will print the fingerprint in a
26generic DNS RR format parsable by most modern name server 22generic DNS RR format parsable by most modern name server
27implementations. If your nameserver has support for the SSHFP RR, as 23implementations. If your nameserver has support for the SSHFP RR
28defined by the draft, you can omit the -g flag and ssh-keygen will 24you can omit the -g flag and ssh-keygen will print a standard SSHFP RR.
29print a standard RR.
30 25
31To publish the fingerprint using the DNS you must add the generated RR 26To publish the fingerprint using the DNS you must add the generated RR
32to your DNS zone file and sign your zone. 27to your DNS zone file and sign your zone.
33 28
34 29
35(3) Enable the ssh client to verify host keys using DNS 30(2) Client: Enable ssh to verify host keys using DNS
36 31
37To enable the ssh client to verify host keys using DNS, you have to 32To enable the ssh client to verify host keys using DNS, you have to
38add the following option to the ssh configuration file 33add the following option to the ssh configuration file
@@ -49,4 +44,4 @@ the remote host key, the user will be notified.
49 Wesley Griffin 44 Wesley Griffin
50 45
51 46
52$OpenBSD: README.dns,v 1.1 2003/05/14 18:16:20 jakob Exp $ 47$OpenBSD: README.dns,v 1.2 2003/10/14 19:43:23 jakob Exp $