usnistgov/macos_security
1
0
Fork 0
mirror of https://github.com/usnistgov/macos_security.git synced 2026-02-03 14:03:24 +00:00
Code Issues 21 Actions Packages Projects Releases Wiki Activity

os_sshd_unused_connection_timeout_configure for dev_sonoma typo error #149

New Issue
Closed
opened 2026-01-19 18:29:24 +00:00 by michael · 1 comment
michael commented 2026-01-19 18:29:24 +00:00
Owner
Copy Link

Originally created by @cipineda on GitHub.

Originally assigned to: @robertgendler on GitHub.

Summary

The os_sshd_unused_connection_timeout_configure for dev_sonoma as a typo error that is causing sshd config to fail.

The code looks and writes unusedconnection**e**timeout when it should be unusedconnectiontimeout on the file /etc/ssh/sshd_config.d/01-mscp-sshd.conf

(Summarize the bug encountered concisely)

Steps to reproduce

/usr/sbin/sshd -G | /usr/bin/grep -c "^banner /etc/banner"
/etc/ssh/sshd_config.d/01-mscp-sshd.conf: line 35: Bad configuration option: unusedconnectionetimeout
/etc/ssh/sshd_config.d/01-mscp-sshd.conf: terminating, 1 bad configuration options

Operating System version

macOS Sonoma 14 Beta 7 (23A5337a)

Intel or Apple Silicon

both

What is the current bug behavior?

/usr/sbin/sshd -G | /usr/bin/grep -c "^banner /etc/banner"
/etc/ssh/sshd_config.d/01-mscp-sshd.conf: line 35: Bad configuration option: unusedconnectionetimeout
/etc/ssh/sshd_config.d/01-mscp-sshd.conf: terminating, 1 bad configuration options

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

/etc/ssh/sshd_config.d/01-mscp-sshd.conf: line 35: Bad configuration option: unusedconnectionetimeout
/etc/ssh/sshd_config.d/01-mscp-sshd.conf: terminating, 1 bad configuration options

Possible fixes

Replace the unusedconnectionetimeout with unusedconnectiontimeout on the remediation script for the os_sshd_unused_connection_timeout_configure

Originally created by @cipineda on GitHub. Originally assigned to: @robertgendler on GitHub. ### Summary The os_sshd_unused_connection_timeout_configure for dev_sonoma as a typo error that is causing sshd config to fail. The code looks and writes `unusedconnection**e**timeout` when it should be `unusedconnectiontimeout` on the file `/etc/ssh/sshd_config.d/01-mscp-sshd.conf` (Summarize the bug encountered concisely) ### Steps to reproduce `/usr/sbin/sshd -G | /usr/bin/grep -c "^banner /etc/banner"` /etc/ssh/sshd_config.d/01-mscp-sshd.conf: line 35: Bad configuration option: unusedconnectionetimeout /etc/ssh/sshd_config.d/01-mscp-sshd.conf: terminating, 1 bad configuration options ### Operating System version macOS Sonoma 14 Beta 7 (23A5337a) ### Intel or Apple Silicon both ### What is the current *bug* behavior? `/usr/sbin/sshd -G | /usr/bin/grep -c "^banner /etc/banner"` /etc/ssh/sshd_config.d/01-mscp-sshd.conf: line 35: Bad configuration option: unusedconnectionetimeout /etc/ssh/sshd_config.d/01-mscp-sshd.conf: terminating, 1 bad configuration options ### What is the expected *correct* behavior? ### Relevant logs and/or screenshots ### Output of checks /etc/ssh/sshd_config.d/01-mscp-sshd.conf: line 35: Bad configuration option: unusedconnectionetimeout /etc/ssh/sshd_config.d/01-mscp-sshd.conf: terminating, 1 bad configuration options ### Possible fixes Replace the `unusedconnectionetimeout` with `unusedconnectiontimeout` on the remediation script for the `os_sshd_unused_connection_timeout_configure`
michael commented 2026-01-19 18:29:24 +00:00
Author
Owner
Copy Link

@cipineda commented on GitHub:

I sync'd and now see the correction.

@cipineda commented on GitHub: I sync'd and now see the correction.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
michael
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: usnistgov/macos_security#149
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?