On Thursday 23 March 2006 13:15, Jaroslaw Rafa wrote:
> 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...
If I sound snippy, I don't mean that. I'm short on sleep (as is often
the case) and have evaluated this question many times in the past few
weeks, as well as the idea in general over the past few years.
Because at some point I may be making some changes and using features
that are implemented differently on PuTTY than on SSH. I've been
working on this project for 4 years. I have a server, written in Perl,
that handles retrieving data, sorting it, storing it in MySQL, then
pulling data from the db and sending it to my clients, according to the
specifications of each individual client. Then the Agent program,
which is what this would be used with, takes that data and prints it.
The last time I had any estimate of size was a grossly underestimated
size of 15,000 lines of code for the server. That is without including
a number of libraries and binaries and without including the Java
source for the Agent program and the Setting Editor, which was in
Javascript and will soon be completely redone in Java.
It is NOT easy to maintain a code base of this size with only one person
on it -- especially if most of that person's time is still focused on
writing new software instead of maintaining existing code. Even with
notes and comments, it is difficult to keep up with a codebase that
size. I've found it pays off, many times over, to take extra time to
do it right the first time. While it may seem like a simple thing to
change the executable's name, and that would be in notes, in a year, I
may forget it, may look over notes and misunderstand them, or run into
similar problems. Having an executable named ssh when it is putty is,
in this case, a premeditated failure. This is one reason I wrote the
Agent program in Java, so I could write it once and have only one or
two classes that deal with the differences between Windows and Linux.
It's paid off for me many times over and made it much easier to upgrade
or add to the code.
This stubborn consistency has saved my butt many times over the past 3
years -- 3 years, instead of the 4 I've been at it because it took me a
few nasty required rewrites to realize consistency works best.
> > > 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.
I didn't realize that.
If I could, I'd recompile libc statically on my own and do the same for
the few other libraries needed for stunnel. In the meanwhile, I've
received some info regarding my Java forwarder, so I'm going to go over
that and if the major problems there are solved, I may end up producing
a Java forwarder that does what I need. (I've seen and tested a few in
Java, but the tend to crash!)
hal
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
