Bug 2374 - please make single(!) addresses that cannot be bound to not failing sshd startup
Summary: please make single(!) addresses that cannot be bound to not failing sshd startup
Status: CLOSED WONTFIX
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: 6.7p1
Hardware: Other All
: P5 enhancement
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-03 05:44 AEDT by Christoph Anton Mitterer
Modified: 2021-04-23 15:11 AEST (History)
2 users (show)

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 Christoph Anton Mitterer 2015-04-03 05:44:18 AEDT 
Hi.

Maybe it's just me, but it happens every now and then that I lock out myself of a system because of wrong ListenAddress lines, i.e. addresses sshd cannot bind to.

It would be nice if sshd would ignore these errors, but for security reasons of course *only* if it can bind to at least one of the named addresses (or if it would instead NOT simply bind to the wildcard address).

At least right now I don't see any security implications of this behavioural change.


Cheers,
Chris.
Comment 1 Darren Tucker 2015-04-13 19:06:49 AEST 
I'm not sure this is a good idea: you'll have a configuration error that is ignored.  I'd suggest logging into the machine you're reconfiguring in a new window/tab/screen session instead of logging out and logging in again (or even just "ssh localhost").
Comment 2 Damien Miller 2020-01-25 23:53:45 AEDT 
I agree with Darren here - we don't plan to add this, sorry.
Comment 3 Damien Miller 2021-04-23 15:11:01 AEST 
closing resolved bugs as of 8.6p1 release