| |
inetd FTW (mod -2/2)
by Anthony (68.145.117.155) (undeadly@arbitraryconstant.com) on Thu Dec 6 04:30:29 2007 (GMT)
|
| |
Use a command line like:
/usr/bin/ssh ssh -T -q -q -e none -i $MYKEY $USER@HOST
in inetd, using a key bound to a socat command on the other end. This avoids the need for persistent SSH connections or daemons to manage them, but also avoids the need to use custom command lines in stuff that doesn't necessarily support it, or support it well. Completely transparent, if you can stomach the lag in establishing the connection.
|
| |
[ Show thread ] [ Mod Up ] [ Mod Down ]
|
|
|
| |
Re: Multiple ssh tricks. (mod -2/2)
by Anonymous Coward (195.241.94.180) on Fri Dec 7 07:30:45 2007 (GMT)
|
| |
I get the following error when doing step 5 at my work office:
"Proxy error: 502 Proxy Error (The specified Secure Sockets Layer (SSL) port is not allowed. ISA server is not configured to allow SSL requests from this port. Most Web browsers use port 443 for SSL requests)
|
| |
[ Show thread ] [ Mod Up ] [ Mod Down ]
|
|
|