Hello I was wondering whether anybody has any experience of running sshd successfully on a system with a 'non-bash' shell?
We're using kirkstone 4.0.12 which has openssh 8.9p1 and systemd 250.5. Both ssh and scp work as expected with '/bin/sh -> bash.bash' on the target, but with '/bin/sh -> busybox.nosuid' (ash shell) the connections fail. The sshd logs on the target show: Jul 31 15:24:56 hc sshd[17826]: Connection from UNKNOWN port 65535 on 192.168.12.246 port 65535 Jul 31 15:24:56 hc sshd[17826]: debug1: kex_exchange_identification: write: Broken pipe Jul 31 15:24:56 hc sshd[17826]: banner exchange: Connection from UNKNOWN port 65535: Broken pipe Some extra debug messages that I've added to both systemd and sshd show that the incoming socket gets closed somewhere between the handover from the systemd socket service to the systemd sshd service. This results in sshd being unable to get any peer details. I can't see anything obvious in either the systemd source or sshd source that suggest a dependency on bash. Any ideas gratefully appreciated. Regards Mark -- *Mark Corbin * Senior Software Engineer | lunarenergy.com <https://www.lunarenergy.com> | LinkedIn <https://www.linkedin.com/company/lunarenergyinc/> | Instagram <https://www.instagram.com/lunarenergyinc/> [image: Lunar Energy Logo] -- C2:Restricted unless otherwise stated. -- Lunar Energy Limited is a company registered in England and Wales, authorised and regulated by the Financial Conduct Authority under reference number 767876. Company registration number: 05631091. Registered office: 55 Baker Street, London, England, W1U 7EU
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63634): https://lists.yoctoproject.org/g/yocto/message/63634 Mute This Topic: https://lists.yoctoproject.org/mt/107648648/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
