6/30 I asked another host machine to install a ssh client so that I could
telnet there and then ssh to soda. Thing is, I can't connect
because soda doesn't support ssh protocol v2. Does anyone know
about plans to change this?
\_ there's a slightly easier way to do this and it doesn't involve
asking someone else to install something for you.
\_ when data fellows makes their ssh2 implementation less stupid
about their license.
\_ ssh2 is still in testing and not free for use. Have them install
ssh1 as well.
\_ Ride BIKE!
\_ Compile your own.
\_ Interestingly (to me anyway), this only puts the security breach
one step back. Instead of a cracker sniffing your soda account,
\_ the point is that soda's subnet is filled with lemurs.
they can sniff your other telnet account, and then ssh from there
to soda and wreak all sorts of terrible havok!
\_ Telneting somewhere just to be able ssh to soda is a really
stupid idea. It not only defeats the security that the soda
admins are trying to establish, but also compromises the other
account as well. Get off your ass and install ssh on your owm
machine or explore the possibility of using s/key.
\_ The soda admins are trying to protect against sniffers on this
subnet. Telnet->ssh is no dumber than purely telnet,
and given the number of lemurs probably a bunch safer. |