Package: openssh-client
Version: 1:6.9p1-2+b1
Followup-For: Bug #618863
It appears that /usr/bin/ssh still does not verify the DNS
information properly. What's the status of this issue? What is
upstream's take? Has this issue been taken upstream?
-- System Information:
Debian Release: stretch/sid
Package: openssh-client
Version: 1:6.0p1-4
Followup-For: Bug #618863
openssh now includes a configure option to link to ldns for verification of
the dnssec service rather than relying on the +ad bit in a response for a
resolver. Maybe it would be worth adding that to the configuration options on
t
On Fri, Mar 18, 2011 at 07:41:36PM -0700, Rob Leslie wrote:
> When the VerifyHostKeyDNS option is used, ssh attempts to verify unknown
> remote host keys by looking up SSHFP records in DNS. It relies on the AD
> (Authentic Data) flag in the response to determine whether the fingerprint
> it receive
Package: openssh-client
Version: 1:5.5p1-6
Severity: normal
File: /usr/bin/ssh
Tags: upstream
When the VerifyHostKeyDNS option is used, ssh attempts to verify unknown
remote host keys by looking up SSHFP records in DNS. It relies on the AD
(Authentic Data) flag in the response to determine whether
4 matches
Mail list logo