|
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Expert-to-Expert. Learn advanced UNIX, UNIX commands, Linux, Operating Systems, System Administration, Programming, Shell, Shell Scripts, Solaris, Linux, HP-UX, AIX, OS X, BSD. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Tunneling NFS through SSH???? | ImpeccableCode | Filesystems, Disks and Memory | 3 | 05-02-2008 10:50 AM |
| SSH Tunneling | silvaman | UNIX for Advanced & Expert Users | 1 | 02-27-2007 03:57 PM |
| Tunneling | ErNci | UNIX for Advanced & Expert Users | 2 | 10-07-2005 07:43 AM |
| Sniffing an established port | matrixmadhan | IP Networking | 5 | 06-16-2005 10:03 AM |
| C Prog to close a socket in established state | teledelux | High Level Programming | 1 | 10-03-2001 12:42 PM |
 |
Powered by 
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
09-11-2009
|
||||
|
||||
|
tunneling commands and file transfers through established ssh connection
Hi - I frequently run commands, and transfer files to/from a host that uses SecurID ssh authentication. It is a real pain to have to enter the authentication information every time I want to interact with this host. I am wondering if there is a way to establish a one-time ssh connection to this host and do everything through this connection. Is this the same as ssh tunneling? For example, I may want to execute a script on my local host that copies files to this host and then submits a pbs job. Is there any way I can do this through the already established ssh connection so that I don't have to enter my authentication information every time as long as the ssh connection remains active. Thanks!
|
|
09-11-2009
|
||||
|
||||
|
Yes, there is a way. Place the following entry in the ~/.ssh/config file. Code:
host *
controlmaster auto
controlpath /tmp/test_ssh-%r@%h:%p
So whenever you make the first connection, it will create a socket and further connections will be tunneled through that, and no authentication after the first connection & it is also until it persists. You can change the control path, also you can control it for particular hosts. Let us know whether it helped ?! |
|
| Bookmarks |
| Tags |
| ssh, tunneling |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Hybrid Mode
