Bug 457 - SSHD doesn't start when using invalid port numbers
Summary: SSHD doesn't start when using invalid port numbers
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: -current
Hardware: ix86 Linux
: P2 major
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-17 11:14 AEDT by Johann Burkard
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Johann Burkard 2002-12-17 11:14:59 AEDT 
When using invalid port numbers, SSHD doesn't want to start up. Imagine you made
a typo and sshd_config lists

port=601337

# /usr/sbin/sshd start 
/etc/ssh/sshd_config line 9: Badly formatted port number.  

If I start a piece of software, the software must assume that I want to use it.
If SSHD encounters an invalid value, it should handle the error (maybe by
binding to port 22 and logging the error). It should not just exit - software
should be error-tolerant and this isn't.
Comment 1 Ben Lindstrom 2002-12-17 11:51:07 AEDT 
Starting a service when the configuration is incorrect.  Mainly when it is a very important like a port is outright wrong.  OpenSSH acts correctly
Comment 2 Damien Miller 2004-04-14 12:24:18 AEST 
Mass change of RESOLVED bugs to CLOSED