Thomas Sapp wrote:
> I would use SSH except I am not allow to install software on my work
> computer that is not approved by my company, freeware or not.
Jason Costomiris wrote:
> So use putty, but don't get the installer.
>
> Unzipping and running != installing.
Do you think that Thomas' network administrators would agree with that?
In many places, trying that sort of logic would be counted as an
aggrevating factor, making the perpetrator *more* likely to be fired.
I'd also suggest that telnet still has a place. That includes when the
telnet sessions are encrypted (for example, through a VPN), go over a
trusted network, or where the local security on the rest of the network
is not high.
For example, some of the password hashes that Windows Networking uses
are known to be very weak. It's not supposed to be much harder to get
the passwords out of Windows than it is to get passwords out of telnet.
In small offices, this usually isn't a problem: everyone knows and
trusts everyone else on the network. (Besides, there are more than
enough other ways that a malicious insider could cause trouble...)
If you've got telnet set up, working, and the users know the interface
(especially when they're using Windows telnet-only interfaces) it may
not be worth the hassle to switch.
James.
--
E-mail address: james@ | "I've never understood the appeal of "Big Bother" - I
westexe.demon.co.uk | guess having lived for 3 years in a house shared with
| Geography students sorta numbs the appeal ..."
| -- "Tanuki"
