Re: openssh-3.7.1p2 "Nasty PTR record"

From: Darren Tucker (dtucker_at_dodgy.net.au)
Date: 09/26/03 

Date: Fri, 26 Sep 2003 07:29:09 GMT

In article <pan.2003.09.26.04.22.33.327502@gpv.co.nz>,
Graham Vincent <graham@gpv.co.nz> wrote:
>> It looks like the getaddrinfo() function on your platform (you don't say
>> what that is) does not behave as the OpenSSH authors expect, and as is
>> documented on other platforms.

If that's the case you can add "#define BROKEN_GETADDRINFO 1" to
config.h and recompile. That will force the use of OpenSSH's
getaddrinfo/getnameinfo replacement functions. 

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

Relevant Pages

  • Re: openssh-3.7.1p2 "Nasty PTR record"
    ... This check was added to address the following quirk of OpenSSH: ... It looks like the getaddrinfo() function on your platform (you don't say ...
    (comp.security.ssh)
  • Re: openssh-3.7.1p2 "Nasty PTR record"
    ... This check was added to address the following quirk of OpenSSH: ... It looks like the getaddrinfo() function on your platform (you don't say ...
    (comp.security.ssh)
  • Re: openssh-3.7.1p2 "Nasty PTR record"
    ... >>It looks like the getaddrinfo() function on your platform (you don't say ... >>what that is) does not behave as the OpenSSH authors expect, ...
    (comp.security.ssh)
  • Re: openssh-3.7.1p2 "Nasty PTR record"
    ... >>It looks like the getaddrinfo() function on your platform (you don't say ... >>what that is) does not behave as the OpenSSH authors expect, ...
    (comp.security.ssh)
  • Re: openssh-3.7.1p2 "Nasty PTR record"
    ... > This check was added to address the following quirk of OpenSSH: ... > It looks like the getaddrinfo() function on your platform (you don't say ...
    (comp.security.ssh)