7/14 My company firewall doesn't allow port 22 connection. What should
I do? And getting my ignorant IS management people to open this port
is probably harder than sleeping with their wives. Is there an
alternative way to ssh to soda?
\_ If you find a port that your firewall allows, let us know and
we can probably set up an extra sshd on that port. --mconst
\_ Try the port redirector I just installed on scotch (look three
motd entries up). --mconst
\_ Thanks. It works.
\_ I find it very easy to sleep with IS management's wives.
\_ Everyone who isn't an IS manager does.
\_ .forward your email. Your soda account by default is insecure
since it is run and used by a bunch a hackers.
\_ Huh? How much more off topic could you get?
\_ anyone notice you can telnet to another server and ssh from there?
\_ Anyone notice how this COMPOUNDS the problem? Don't. --sowings
\_ The PROBLEM is that soda isn't allowing telnet any more.
So no, it doesn't compound the problem
\_ Soda allows telnet. It doesn't allow cleartext passwords.
Don't get mad, get clue.
\_everything running over the telnet will be free game, before
it gets encrypted.
\_ that was my point... a mandatory ssh on soda won't
necessarily force people to be safe...
\_ clue time: you can never force people to be safe.
\_ then why mandatory ssh?
\_ cuz smart people will simply download the software
and use ssh on the machine they're sitting at
instead of doing a roundabout telnet into another
machine. which one is more of a hassle?
apparently some people think it's more convenient
to telnet then ssh each time. but then again,
berkeley admits some pretty stupid people.
\_ Worse yet, they give them degrees. |