On Tue, Dec 12, 2000 at 05:30:05PM +0200, Johan P. Fourie wrote:
> I'm trying to get SSH2 2.3.0 on Linux configured so that it creates a
> tunnel for a
> certain port at startup (rather than having to log in and start it
> manually).
> Currently it only works while you are logged in and in a forked shell
> after SSH2
> initialized. SSH2 do not support backgrounding, and I was hoping for a
> "work-around" to this problem.
I have run into the same problem on a few occasions... what I ended up
doing was just using SSH1 protocol, or in some cases (as appropriate),
use stunnel.
In my case I had to bind to a privileged port but make the connection as
a non-privileged user, so I had to execute ssh as root but use the -i
parameter to use another user's key file. This failed miserably for me,
because it would always prompt me for the passphrase despite using a key
with an empty one. IMHO, there is something seriously broken in SSH2
(IIRC I had the same problem with the commercial ssh but it's been a
while and I'm not sure); seems to me like an implementation issue and
not a protocol issue in my case though. I asked the developers about it
and after a few cycles back and forth, I eventually stopped getting
responses and my worst fears were realized. ;P
There are better ways I'm sure though. ;) But if all else fails, at
least you have something to fall back on. :-\
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
