search for: user_add_ssh_key

...users a uniform passwd entry with only the username/shadow hash changing. This entry will have a fixed UID, GID, shell and homedir, and this fixed homedir will contain an authorized_keys file that will dynamically contain keys as set for our appliance's users (I'll add the CLI command "user_add_ssh_key" or something). While the above solution is, like I said, obvious, it has a very severe drawback I'm not sure how to tackle, and that's the fact that nsswitch modules are system global. I don't want our hosts' Linux users (root, nobody, daemon, etc) to collide with the applian...