Bug 79972 - Segmentation fault when sshing an hostname with no address associated
Segmentation fault when sshing an hostname with no address associated
Product: Red Hat Raw Hide
Classification: Retired
Component: openssh (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Brian Brock
Depends On:
Blocks: 79578
  Show dependency treegraph
Reported: 2002-12-18 03:47 EST by Nicolas Mailhot
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-08 03:46:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nicolas Mailhot 2002-12-18 03:47:35 EST
On RH8, when sshing an hostname with no address associated, I get a :

[nim@poseidon nim]$ ssh fr
ssh: fr: No address associated with hostname


On Rawhide (same user and nfs-mounted home) :

[nim@ulysse nim]$ ssh -v fr
OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /home/nim/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
Erreur de segmentation


Don't know if it's serious or purely cosmetic, but a core command as ssh should
be crashproof IMHO
Comment 1 Brian Brock 2003-01-07 19:58:22 EST
I can't replicate this error (same version of ssh, more recent versions of many
underlying packages like glibc), I get a sane exit without segmentation fault.

Is the error occuring?  If so, is there more background information you can
provide on the system's configuration (changes from default setup in openssh,
any libraries not from the current rawhide)?
Comment 2 Nicolas Mailhot 2003-01-08 03:46:04 EST
I can't reproduce it either now. My openssh version didn't change ; however I
did a couple of rawhide syncs since the report, so probably the problem was in
another rpm that changed since then. I'll close the bug.

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