<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-im" style="color:rgb(80,0,80)"><div dir="ltr" class="gmail_attr">On Thu, Aug 1, 2024 at 8:41 AM Mark Corbin <<a href="mailto:mcorbin@lunarenergy.com" target="_blank">mcorbin@lunarenergy.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello<div><br></div><div>I was wondering whether anybody has any experience of running the sshd service successfully on a system with a 'non-bash' shell?</div></div></blockquote><div><br></div></span><div>mark, this is a systemd list, people here may know about openssh but it is not the right place to ask</div></blockquote><div> </div><div>Hello Cristian</div><div><br></div><div>My reason for posting to the systemd list is because this currently looks like a systemd issue and not an openssh issue. Sorry if I didn't make that clear:</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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. The call to <span style="color:rgb(0,0,0);font-family:monospace">getpeername</span><span style="color:rgb(0,0,0)"><font face="arial, sans-serif"> in </font></span><span style="color:rgb(0,0,0);font-family:monospace">service_spawn </span><span style="color:rgb(0,0,0)"><font face="arial, sans-serif">fails with ENOTCONN.</font></span><br></blockquote><div><br></div><div>My investigation so far shows that the systemd socket service listens for incoming ssh connections, accepts incoming connections and prepares to spawn the sshd service, but somewhere during this process the socket gets closed before sshd is spawned. Tracing through the systemd code shows that the socket has been closed by the time <font face="monospace">getpeername</font> is called in <font face="monospace">service_spawn</font> (the call fails with ENOTCONN). This is immediately before systemd attempts to spawn the sshd process in <font face="monospace">src/core/service.c</font>.</div><div><br></div><div>Regards</div><div><br></div><div>Mark</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 3 Aug 2024 at 18:25, Cristian Rodríguez <<a href="mailto:crrodriguez@opensuse.org">crrodriguez@opensuse.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 1, 2024 at 8:41 AM Mark Corbin <<a href="mailto:mcorbin@lunarenergy.com" target="_blank">mcorbin@lunarenergy.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello<div><br></div><div>I was wondering whether anybody has any experience of running the sshd service successfully on a system with a 'non-bash' shell?</div></div></blockquote><div><br></div><div>mark, this is a systemd list, people here may know about openssh but it is not the right place to ask.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>I can't see anything obvious in either the systemd source that suggests a dependency on bash.</div><div><br></div><div><br></div></div></blockquote><div><br></div><div>IF systemd wants bash, it would explicitly call /bin/bash or have scripts with the proper shebang. otherwise a posix compatible shell should work.<br>Shells that are widely tested as default are bash and dash, stick to one of those.</div><div><br></div><div><br></div></div></div>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div><div><br><span style="color:rgb(38,77,116);line-height:1.6;font-size:10pt;font-family:"IBM Plex Sans",sans-serif"><strong>Mark Corbin </strong></span><br><span style="color:rgb(38,77,116);line-height:1.4;font-size:10pt;font-family:"IBM Plex Sans",sans-serif"> Senior Software Engineer | <a href="https://www.lunarenergy.com" target="_blank">lunarenergy.com </a> | <a href="https://www.linkedin.com/company/lunarenergyinc/" target="_blank">LinkedIn</a> | <a href="https://www.instagram.com/lunarenergyinc/" target="_blank">Instagram</a><br></span><img style="padding-top: 5px;" src="https://storage.googleapis.com/lunarenergy/email-sigs/lunarenergy-logo.png" alt="Lunar Energy Logo" width="100"></div></div></div>
<br>
<font size="1">C2:Restricted unless otherwise stated.</font><br>
<br>
<p><font size="1">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</font><br></p>