- Minor
I want to revert the SSH "Improvements".
If you change something like this, atleast document what exactly has changed. I have modified my ssh configurations in the past and now everything is broken from the update. How can I revert ssh back to the way it was before?
I also now have a problem with docker now when using a command that runs inside docker:
WARNING: Error loading config file: /root/.docker/config.json: stat /root/.docker/config.json: permission denied
no idea how to fix this. there is no such config file but I guess there should be, but it wasn't created before because of all the permission changes? I noticed access to /root is messed up now. Even non root users are redirected to create configs inside /root instead of own /home directories? How can I revert this? There is NO benefit for security. Forcing everything to run as root is the opposite of security. Why force that? Inside passwd the home directory is set up correctly, but logging in as that user, all configs are pulled from /root instead which results in permission error...
Some examples:
logging in as non-root user
-bash: cd: /root: Permission denied
-bash: /root/.bash_profile: Permission denied
trying to run mc as non-root:
draic@Prospero:/home/draic$ mc
Failed to run:
Cannot create /root/.config/mc directory
Rant:
Personally this feels like a shoehorned attempt at security improvements for an outdated way to handle users. Instead of furthing sticking with using a root user (and root user only), there should be a rework of user management on unraid. I do not use ssh to run stuff on unraid, but to run stuff in docker containers that are hosted on unraid. This always felt way to hacky to achieve on unraid, but now I feel like being forced to switch OS because I can't utilize docker the way I want and need to.
-
1
