On Sun, Jun 22, 2008 at 5:39 AM, Kapil Hari Paranjape <[EMAIL PROTECTED]>
wrote:

> Hello,
>
> On Sat, 21 Jun 2008, Raja Subramanian wrote:
> > it is easy to establish more than N connections per minute over
> > the LAN through regular usage through various shell scripts, maintenance
> > tasks, etc.
>
> Multiple ssh connections are not really required for recent openssh
> clients. These create a local "connection socket" which allows
> multiple ssh clients to operate through one TCP connection.
>
> For example my config file for a specific client looks like:
>
> Host    somename
> User    myname
> ControlPath     ~/.ssh/%r.%h.sock
> ControlMaster   auto
> StrictHostKeyChecking yes
> IdentityFile ~/.ssh/myid_dsa
> PasswordAuthentication no
> UserKnownHostsFile ~/.ssh/known_hosts
> ForwardX11 no
> ForwardAgent no
>
> As a consequence, if I log in to "somename" once, then the
> same TCP connection can be re-used by other clients---without
> re-authentication. This is most useful if I later need to "scp" a file
> to the "somename" while remaining connected.
>
> Regards,
>
> Kapil.
> --
>
> Hi Kapil,

I use ssh and screen for my training sessions, It helps me to share my
terminal with them. Here session is very interactive so that, my self as
well as my trainees work on the same single screen.

Each time every one has to pass ssh authentication, is that any way to by
pass authentication.  they use putty and try to connect from windows
workstations.


any clue ??

cheers


Ravi jaya
_______________________________________________
To unsubscribe, email [EMAIL PROTECTED] with 
"unsubscribe <password> <address>"
in the subject or body of the message.  
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc

Reply via email to