Tiny Core Base > piCore Test Releases
piCore-12.0beta1
mortegai:
--- Quote from: Rich on October 06, 2020, 03:52:41 PM ---Hi Juanito
Another way to test if group sshd exists.
Change this:
--- Code: --- busybox groups sshd >/dev/null 2>&1
[ $? -ne 0 ] && busybox addgroup -g 33 sshd
--- End code ---
To this:
--- Code: --- touch /tmp/groups
chown tc:sshd /tmp/groups >/dev/null 2>&1
[ $? -ne 0 ] && busybox addgroup -g 33 sshd
--- End code ---
--- End quote ---
Or just change to
--- Code: --- grep -q sshd /etc/group
[ $? -ne 0 ] && busybox addgroup -g 33 sshd
--- End code ---
Rich:
Hi mortegai
If you are going to do that, search for an exact match:
--- Code: ---grep -q '^sshd:' /etc/group
--- End code ---
Juanito:
--- Quote from: mortegai on October 06, 2020, 03:41:51 PM ---But now, if the sshd user does not exist (initial/pristine situation) occurs error:
Privilege separation user sshd not exist
and sshd does not run.
--- End quote ---
sshd ran on startup for me in testing using the modified openssh init.d script, but I presume now that was influenced by the backup.
I don't know of a reason why an additional user named sshd would be necessary for sshd to work on piCore - things work on Core/CorePure64 without it.
I will have access to a screen in a couple of days time to be able to troubleshoot.
Rich:
Hi Juanito
Seems this already came up in piCore-12.0alpha1:
http://forum.tinycorelinux.net/index.php/topic,24196.msg153179.html#msg153179
Paul_123:
If you could interpret anything he said..... lol.
groups sshd was a carry over from piCore 11 (and possibly 10) Its just that Juanito and I were trying to commonize configs between x86_64 and piCore. We started with busybox, which is why "groups" got dropped and highlighted this issue.
We just have to figure out right solution.....without doing a big re-invention.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version