Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 189997 - Nasty PTR record from ssh and segfault in glibc
Nasty PTR record from ssh and segfault in glibc
Status: CLOSED DUPLICATE of bug 190002
Product: Fedora
Classification: Fedora
Component: glibc (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-04-26 11:27 EDT by Jon Masters
Modified: 2007-11-30 17:11 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-27 05:53:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Testcase (587 bytes, text/plain)
2006-04-27 05:44 EDT, Tomas Mraz
no flags Details

  None (edit)
Description Jon Masters 2006-04-26 11:27:41 EDT
Description of problem:

Openssh refuses incoming connections and returns errors in the logs:

Nasty PTR record "perihelion.int.jonmasters.org" is set up for, ignoring

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. ssh into box
2. it fails
Actual results:

Cannot connect via ssh

Expected results:

Can connect to box

Additional info:

Tomas says it might be a problem glibc with a change in sematics to getaddrinfo.
Comment 1 Jon Masters 2006-04-26 11:40:37 EDT
Setting "UseDNS no" in sshd_config works around the problem temporarily.
Comment 2 Tomas Mraz 2006-04-27 05:44:14 EDT
Created attachment 128294 [details]

Here is the testcase.
Comment 3 Tomas Mraz 2006-04-27 05:48:17 EDT
So this is definitely a bug in glibc. At least it shouldn't segfault and I think
the semantics shouldn't change either.
Comment 4 Jakub Jelinek 2006-04-27 05:53:32 EDT

*** This bug has been marked as a duplicate of 190002 ***

Note You need to log in before you can comment on or make changes to this bug.