3/20 \_ what about the broken sshd? -tom
\_ Its not broken. It works fine for SSHv1
and OpenSSH clients. Get a different client.
\_ what would you call a server that violates
protocols? I would call it broken. The
fact that openssh clients also violate
protocols doesn't make the server any
less broken. And, once again, there's
ABSOLUTELY NO ADVANTAGE TO USING OPENSSH.
-tom
\_ Totally there is! Open source!
\_ Why don't we run both versions? Run
the non-OpenSSH version of port 69
so that tom will shutup.
\_ Uh, its free and it comes preinstalled
with *BSD, MacOS X, Linux, etc.
WTF would I want to download something
extra from http://ssh.com that isn't nearly
as well audited as OpenSSH and isn't
free for corporate users?
\_ what difference does it make
whether it's free for corporate
users? You would want to download
it because IT SUPPORTS MORE CLIENTS.
Are you really this stupid? -tom
\_ Because some of us are corporate
users, not gub'ment 'ployees.
\_ we're not talking about what
you install in your cube.
you can connect to soda
if it's not running openssh.
-tom
http://ssh.com's ssh server doesn't like _/
OpenSSH clients and it doesn't like
NiftyTelnet SSH on the mac (ie it will
randomly drop my connection and scp
doesn't work right), both of
which currently work with soda's
OpenSSH server. No reason to switch
since switching would reduce the
number of clients that are supported.
\_ Bullshit. I am using both openssh clients and
NiftyTelnet with http://ssh.com's server and they work
fine. -tom
\_ since you clearly are not making any
progress getting the powers that be to
switch from OpenSSH, why don't you
harass the OpenSSH people and get them
to fix it?
\_ So, you like the added bloat of having
to start the ssh1 daemon every time an
ssh1 client connects? Once OpenSSH
supports shession rekeying (promissed in
the next major release) there will be
no reason not to use OpenSSH. |