Hi @ovim,

I’m just going to throw some random fixers for such issues and let me know if you’ve tried them or if not, will you try them.

So first, as you’ve mentioned let’s see the /dev/random and /dev/urandom part.

Check permissions on random numbers generators, the “others” must have “read” access to these devices:

# ls -l /dev/random /dev/urandom
crw-r--r-- 1 root system 39, 0 Dec 28 10:48 /dev/random
crw-r--r-- 1 root system 39, 1 Dec 28 10:48 /dev/urandom

If the permissions are different, you can change them as follows:

chmod o+r /dev/random /dev/urandom

Then restart your SSHD service

stopsrc -s sshd
startsrc -s sshd

If you are still getting the same issue, try removing urandom and random and creating them again.

stopsrc -s sshd
rm -rf /dev/random
rm -rf /dev/urandom
mknod /dev/random c 39 0
mknod /dev/urandom c 39 1
randomctl -l
ls -lad /dev/random /dev/urandom
startsrc -s sshd