https://bugzilla.mindrot.org/show_bug.cgi?id=3875
Bug ID: 3875
Summary: SSH client behavior breaks non-interactive sudo/stdio
handling used by Ansible (automation times out waiting
for privilege escalation)
Product: Portable OpenSSH
Version: 10.1p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Miscellaneous
Assignee: [email protected]
Reporter: [email protected]
After upgrading to OpenSSH 10.1p1 on Slackware64-current, both Ansible
ad-hoc commands and playbooks that use sudo/become started failing with
“Timeout (12s) waiting for privilege escalation prompt.”
Downgrading OpenSSH immediately fixes it. Disabling SSH multiplexing
(ControlMaster/ControlPersist) also fixes it, confirming the issue is
in the client’s multiplexing path. Reproducible by running any playbook
with become: yes on multiple Linux hosts. This regression prevents
Ansible from detecting the BECOME-SUCCESS marker over a multiplexed
connection, causing privilege escalation tasks to hang and fail.
If any other info is needed just let me know.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
[email protected]
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
