Hal Vaughan napisal(a):
> > So, what's the problem with using one command name ("plink") in the
> > Windows batch file and another ("ssh") in the Linux shell script?
> > Because probably this will be the only difference - plink is, in
> > fact, nothing more and nothing less than a Windows implementation of
> > the Linux's "ssh" command...
>
> See above. It becomes a nightmare in the long run in trouble shooting
> and with other issues. I'm one person maintaining the code and trying
> to keep different arguments and settings is a nightmare.
Hm... so, just rename "plink.exe" to "ssh.exe" on your disk, and this way
you will have the same command name (and probably arguments) on both
systems...
You can do similar thing on the Linux side as well - just create a symlink
to '/usr/bin/ssh' called 'plink' in your current directory at the very
beginning of your script, and you're done...
I still don't understand where's the problem...
> > Surely it depends on OpenSSL. I don't know if it's possible at all to
> > compile statically with this library.
>
> Stunnel does. PuTTY does not, believe it or not.
Yes, I was speaking about stunnel, not PuTTY. No SSH client, including
PuTTY, and Linux native client as well, depends on SSL libraries, as SSH
does not use SSL but it's own encryption engine that's built right into the
server and client.
Regards,
Jaroslaw Rafa
[EMAIL PROTECTED]
--
Spam, wirusy, spyware... masz do6f? Jest alternatywa!
http://www.firefox.pl/ --- http://www.thunderbird.pl/
Szybciej. #atwiej. Bezpieczniej. Internet tak jak lubisz.
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
