Trying to setup SSH accounts to work with public key authentication, and after creating the directory and authorized_keys file, setting perms, etc, it all works fine. I restart the device to test and all of the changes to it are gone… essentially as if the thing has just re-imaged itself.
Some background as to why I want to bother: We purchased the device to make some remote backups to keep off-site of some mission critical materials. Having the features advertised (AD integration, etc), we figured it would function well in an enterprise environment. The ways we had planned on using it originally haven’t panned out, but I was happy to see it could support SSH, which got us around a big hurdle of being able to reach the device easily and programatically from a different network segment. The thing is, SSHing into a system as root with just a password is crazy insecure! We can’t possibly leave the device like that and put anything remotely sensitive on it.
So, I guess what I’m after here is a way to get the system to stop wiping out the /home and /etc/ssh directories so I can get the SSH keys and configurations to stick… or, failing a way to disable whatever is rewriting it, a way to modify the image it is using to include the changes I want.
Have a feeling I may be SOL, and if it had been up to me from the get go I’d of just setup a proper RAIDed workstation on the other end, but don’t want to give up without asking if maybe someone else has run into this and come out on top. Going to see if I can make everything work the way I want over FTP if this doesn’t work out, but I will be so.much.happier if I can get this puppy to do tricks over SSH.