crappy guide to using putty with dopus:
1) download latest version of putty installer from:
the.earth.li/~sgtatham/putty/lat ... taller.exe
2) Add the location of the putty programs folder to the windows path:
etherealmind.com/putty-command-line/
3) Configure a Saved session in putty. In this test, I have created one called "015_test"
a) enter your remote machine hostname & port (usually 22). Select ssh as connection type
b) Go to Category --> Connection -->Data
enter your user id for the remote machine in the auto-login bit
Go to Category -->Connection --> SSH
Check "Enable compression"
Move Blowfish to the position in-between AES and Arcfour
save your settings
c) See the following links if you have problems with the key generation:
Start the program puttygen.exe to generate a public and a private key. Do not use any passphrase. Save this in your putty programs folder
In the putty key generator program, there is a grey box that says "Public key for pasting into openssh authorised_keys file". copy the key
Use putty to ssh into your remote machine and then execute the following linux commands:
[code]cd .ssh
nano authorized_keys # i can use nano generally. if you can't (in order of difficulty try gedit, nedit, joe, vim or vi.
at the end of authorized_keys, paste the public key you copied from the putty key generator program and save the file
exit your ssh session[/code]
d) Go back to the Putty Configuration Window
Go to Category -->Connection --> SSH --> Auth
Enter the path of the saved private key file (press browse). Leave other defaults as such.
Launch your saved session. In my case "015_test"
Enter your password. You should connect in.
Disconnect
Relaunch your saved session. You should not be prompted for a password now.
######################
4) Now you have to configure dopus. This bit can do with lots of improvement as I don't really know much about dopus scripting. this is the skeleton of a proper command. It does the following actions:
-
You need to create a file called iLikeCheese.txt for this example to work.
-
You also need to change the word username to your username as in the example I am uploading the file to my home directory which requires this. Ideally you would create a variable that allows you to specify the path. I think you need the absolute path as I couldn't get it working with ~ instead of /home/username/
-
the copy addtoarchive presents a dialogue for which I selected the format as 7zip-tar-gz, as pretty much all linux distros I know of have the tar command.
-
One issue is that which my (crappy) version of the Dopus command, you need to make sure the source and destination for the addtoarchive dialogue are the same, as it seems to default to src & dest.
-
note that the plink and pscp commands use the putty session shortcut we created earlier 015_test. You can replace this with username@remotemachineName in a variable if you want. This would mean that you can use this button for any remote machine. However, you will be prompted for user id. May have to modify pscp command to make this work though
@firstfileonly
cd {sourcepath}
copy addtoarchive=.tgz
pscp iLikeCheese.tgz 015_test:/home/username/
plink -ssh 015_test tar -zxvf iLikeCheese.tgz
Hopefully you or others reading this may be able to improve this skeleton Dopus command and post it here.
All the best!