3 Commits

Author SHA1 Message Date
Clark Boylan
5f4b5000c8 Fix sshfp record printing
Previously if you ran `sshfp.py foo.opendev.org x.y.z.a` it would spit
out records that look like:

  foo.opendev.org IN SSHFP 1 1 stuffstuffstuff

The problem with this is when you copy this output into the zone file
the lack of a terminating '.' means the record will actually be for
foo.opendev.org.opendev.org.

We address this by splitting on '.' and taking the first element. This
will still be broken for hosts named foo.bar.opendev.org but for now is
a decent improvement.

Change-Id: Ib12f66c30e20a62d14d0d0ddd485e28f7f7ab518
2021-03-05 12:18:13 -08:00
Ian Wienand
e819c26cad launch-node: get sshfp entries from the host
It turns out bionic ssh-keygen doesn't have the "-D" to produce the
sshfp records; switch to logging in and getting these via "ssh-keygen
-r" on the host.

Change-Id: Icb6efd7c4fd9623af24e58c69f8a188a4c1fb4c9
2020-08-20 15:10:01 +10:00
Ian Wienand
3cbb877d43 launch-node : add sshfp records
Add a tool to scan a host and generate the sshfp records to go into
dns.  Hook this into the DNS print out from the node launcher.

Change-Id: I686287c3c081debeb6a230e2a3e7b48e5720c65a
2020-08-04 01:04:37 +00:00