Hi gurus,
I've installed f40 as an lxc container named FED. Default image comes without an ssh server so I "dnf install openssh-server -y" followed by "systemctl start sshd". It fails. journalctl -xeu sshd shows this:
"FED (sshd)[636]: sshd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS"
Inspection of the sshd.service file shows these as part of the [Service] section:
EnvironmentFile=-/etc/sysconfig/sshd ExecStart=/usr/sbin/sshd -D $OPTIONS
Apparently /etc/sysconfig/sshd is supposed to contain at least one named variable ( name appears to be unimportant ). Searches showed the options name to be SSHD_OPTS, journalctl says it is looking for OPTIONS, either work if declared correctly.
OPTIONS= fails because OPTIONS is null OPTIONS='' works because it is defined but empty.
My question is: since the sshd.service file expects -D $OPTIONS shouldn't /etc/sysconfig/sshd define the OPTIONS variable ahead of time? If the user wants to pass values via $OPTIONS they can do so of their own accord but the service should at least start without modification to sysconfig/sshd ( IMHO ).
Does this call for bugzilla?
Thanks, Mike Wright
On 8/25/24 20:07, Mike Wright wrote:
Hi gurus,
<snip/>
Does this call for bugzilla?
This particular host is running a *highly* customized ubuntu. It started at 12.04 and has been continuously *upgraded* without ever doing a do-release-upgrade and is now declaring itself to be a 24.04. It just lacks snapd and most of the recent intrusions. I've run probably 30 or so various and sundry distros and releases on this lxc setup without any problems.
For some reason the same lxc-image of fedora-40 does not complain about missing $OPTION for sshd when run on debian bookworm lxc setup.
I also posted earlier about ssh accepting my key but kicking me out because PAM lacked some [preauth] thing.
ssh'ing into the debian hosted fedora 40 proceeds without complaint.
Sorry for the noise ( methinks the ubuntu box is about to ride off into the sunset. Alas, I knew him well... )