Re: sshfp records

2013-01-22 Thread Richard Hector
On 23/01/13 16:59, Bob Proulx wrote: > Brad Alexander wrote: >> > Rookie mistake from messing with this too late at night. Apparently it >> > only works with fully qualified domain names (therefore working more >> > like dig than host): > I wouldn't call that a rookie mistake. It seems like a miss

Re: sshfp records

2013-01-22 Thread Bob Proulx
map through to the dns name of the host. That just seems like it is missing some maturity in this brand new feature. (I haven't used the feature yet. Thank you for motivating me to look at it at least a little bit.) > Not sure how I'm going to work around this. I may just dispense w

Re: sshfp records

2013-01-22 Thread Brad Alexander
:b8:3f:4e:ff:51:1f:58:5a:14:3a. Matching host key fingerprint found in DNS. Not sure how I'm going to work around this. I may just dispense with sshfp records for the time being, unless something jumps out at me. --b On Tue, Jan 22, 2013 at 1:20 PM, Bob Proulx wrote: > Brad Alexander wrote: &

Re: sshfp records

2013-01-22 Thread Bob Proulx
Brad Alexander wrote: > Has anyone worked with sshfp records for openssh? No. But I do have a suggestion. > I generated sshfp records: > > IN SSHFP 1 1 5490056a2208c8ad2cf869f5c06470450c8a017a > IN SSHFP 2 1 18aef47bc01264709f25ac9daebed236b45b6b45 > > but when I ssh

sshfp records

2013-01-21 Thread Brad Alexander
Has anyone worked with sshfp records for openssh? I generated sshfp records: IN SSHFP 1 1 5490056a2208c8ad2cf869f5c06470450c8a017a IN SSHFP 2 1 18aef47bc01264709f25ac9daebed236b45b6b45 but when I ssh into the host (after deleting the records from .ssh/known_hosts), I get: $ ssh -o