Maybe your SSH keys might not have right permissions.
# /mnt/DroboFS/Shares/DroboApp s/openssh/bin/ssh -i /mnt/DroboFS/home/admin/.ssh/id_rsa it connect with no pwd - it should have, If it didn't work. If you don't do this step, when you run CRON later as root it'll fail. Accept the prompt to add this connection to known hosts. # /mnt/DroboFS/Shares/DroboApp s/openssh/bin/ssh -i /mnt/DroboFS/home/admin/.ssh/id_rsa drobo1 and re-run that command as the root user on drobo2. Run this with the PRIVATE key (id_rsa) and you should log straight into drobo1 with no password I tried adding it to the path but it gets magically overwritten. Unfortunately, the ssh executable is not in the 'PATH' so you have to run it with the full path. $ ssh -p 2222 the directories you did before.Įdit the authorized_keys file with vi, and paste the SSH key into the file and :wp to saveĭrobo2 is going to do all the copying so go back to drobo2. # cat /mnt/DroboFS/home/admin/.ssh/id_rsa.pubįrom your computer logon to drobo1 via OpenSSH on port 2222 Run this and accept the defaults, but please read the bloody prompts at least and make sure the files end up as per belowĬat the pub key and copy that garbage to clipboard Scp* sftp* ssh* ssh-add* ssh-agent* ssh-keygen* ssh-keyscan* cd to the openssh app and list filesĭrobo5N2:~ # cd /mnt/DroboFS/Shares/DroboApps/openssh/binĭrobo5N2:~/Shares/DroboApps/openssh/bin # ls Also, i feel safer messing around on my second drobo. You can do it in reverse but i like the second drobo doing all the work. This is because drobo2 will be running the sync script and needs to connect to drobo1 and pull the files. You need to create the keys on drobo2, and copy the public key to drobo1. Why use OpenSSH at all? Well dropbear is super slow is why.
# chmod 700 -R /mnt/DroboFS/home/admin/.ssh/ # touch /mnt/DroboFS/home/admin/.ssh/authorized_keys If not create them, and set correct permissions. # /mnt/DroboFS/home/admin/.ssh/authorized_keys I am not sure but i think dropbear creates this folder, and this file edit this this lineĪll done, goto the drobo dashboard and stop start the OpenSSH app (down the bottom of all the apps).įrom here on, connecting via putty or SSH is done on port 2222 to take advantage of OpenSSH. # vi /mnt/DroboFS/Shares/DroboApps/openssh/etc/sshd_config Run this to unpack and install (this is basically how you install any drobo ported app)ĭropbear runs on port 22 so i avoid using OpenSSH on that port by changing the config using vi Use putty, or on a mac just ssh to the drobo with the admin username and password Connect to the Drobo Dashboard app again and goto Droboapps. Update your Drobo Firmware and Drobo Dashboard Lastly: Do this at your own risk, and if you don't want to, try it on a new share at least ) its using a sticky bit on at the root level of each share, effectively giving Drobo admin full access to all files on the system. If you are interested in how Drobo can manage to copy the files in the first place. * this is the plan at least I haven't fully compared permissions after copying yet Then i can access my files anyway i like later. I want nice and bland files with the default Drobo permissions. So for my use case I don't want to fight with the old permissions. I use a MAC now, and maybe one day I'll use windows again or a Google table or whatever. Even on a fresh target, once the files are copied i'm going to have the same problems again I think as the permissions will still be there.įor the most part, most of the files have Windows NTFS permissions, but the computers and users i created those files with don't exist anymore. But i never want to have the same problems again either. Starting fresh or just in a new share means you'll have none of these problems. Trying to compare and copy these files was not going so great from one to another doesn't work very well at the best of times. this is because the original data is from many places, has both MAC and Windows permissions all over it, and a bunch of MAC metadata files that i don't like or need. Format the Target Drobo (Its optional but i'll tell you why)
0 kommentar(er)
