Ssh and putty

I really like the integrated sftp-function. But sometimes it is easier to do things on shell (example: deleting recursive files from an outdated sourceof typo3).

How can I make a button, which launches putty with all login-data for the actual connection?

Thank you and greetings from germany.

Yes (and No:)

Yes you should be able to create a button that will launch putty etc. But this will have to be manually created. The button commands can't access the FTP Address Book data directly to create some auto-putty button.

But it should be easy to create a normal button to open Putty. You'll need to check the Putty syntax for a command line function.

Putty Comand line is indeed easy:

putty.exe -ssh user@host

Look at http://the.earth.li/~sgtatham/putty/0.55/htmldoc/Chapter3.html#S3.7 for more options.

But I have a lot of hosts and I don't want to create duplicate entries (ftp and buttons), because I try to avoid redundant data.

I would also like this feature: running a (putty) shell on the current open (s)ftp connection!
Would be really handy if I could run some kind of action which can access details of the open (s)FTP connection!

You can use {sourcepath} when on an ssh site to get what's currently in the location field (including the ftp:// stuff at the start, although it's technically sftp).

So you could pass that to some VBScript which has its own site-to-username mapping and converts it into the PuTTY command syntax. (Or which just connects to that address and leaves the site to ask for the username.)

I can't think of a better way than that.

Any changes to this as of today and some DOpus versions later?
If DOs (S-)FTP client is based on PuTTY, shouldn't it be possible to also bind PuTTY's terminal functions?

Me too, I'd like to have shell access at the same time as secure file transfer.

No, no changes here.

We're considering moving away from PuTTY as maintaining the PuTTY code is problematic, so it's unlikely we would implement anything that tied Opus to PuTTY in that way.

There's still nothing stopping you from making a script which looks at the current source path and runs PuTTY with appropriate arguments, however.

OK, thanx 4 the quick reply :slight_smile: