Could you generate a key pair with ssh-keygen, retrieve the .ssh/authorized keys from the target server, add your public key to the file and then put that back to the server? That might give you a password-less sign on, but of course, it depends if the server locks your account to a directory from which you cannot get to the .ssh directory. The directory might not exist, so you could probably create it, but you will need to make sure the permissions are rwx --- ---

If you already have a key pair generated, consider connecting as normal with SFTP and:-

Code:

sftp> get .ssh/authorized_keys server_keys
:
:
sftp> !cat server_keys .ssh/id_rsa.pub > new_server_keys
sftp> put new_server_keys .ssh/authorized_keys
:
:
sftp> quit
$ sftp remote-server

Of course, this assumes that the remote server put it's authentication files in ~/.ssh and that you can get to it, but it might be worth a try.


Look in ~/.ssh to see if you already have key generated, but to generate a key-pair / pair of certificates, just run ssh-keygen and follow the prompts.



I hope that this helps. It is not tested and perhaps it's just the hacker in me with a twisted mind, but this might get you going and ease the SFTP to becoming:-

Code:

sftp -b sftp.cmds server

... where sftp.cmds is a plain file containing the cd, get, put or whatever commands to execute when connected.




Robin
Liverpool/Blackburn
UK