setup: straightforward. Instead of password-auth, keyauth can be used. When keypairs are generated using “ssh-keygen -t rsa -b 4096” then they are accepted. A passphrase should be used to protect the private key.
pro: uncomplicated to setup
pro: works directly in both directions
approach: frontend for ssh/rsync binaries
had to extend sshd_config on server to “KexAlgorithms diffie-hellman-group-exchange-sha256,diffie-hellman-group1-sha1”
dsa private/pubkey get generated, pubkey gets used for authentication
configured /storage/sdcard0/sync as syncdir
looks like nice setup. For my usecase I created 2 profiles, one for sending and one for receiving. After fiddling a bit with pathes in both profiles, I can run both profiles and have the files synced.
By default, also newer files on the remote site will be overwritten. To work around this, you have to add “-u” in both profiles to the rsync command which is used.
uses established ssh/rsync protocols
takes a bit time to setup
keyphrase for authentication can not be passphrase protected
2 profiles have to be run for the full sync
syncing with additional systems required additional thinking (i.e. to keep the directory synced between 3 or more systems)
cons: heavy for my usecase, PHP
software/filesync.txt · Last modified: 2018/06/10 02:25 by chris