I tried to enable inbound telnet....but no daemon. the inetd.conf points to a non-existent in.telnetd

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

Any reason you can't use SSH ?

If you need help setting it up, I'd be more than glad to give you a hand. I even know some stupid ssh tricks

Feel free to add me to your IM if you want.

Rob

If you are trying to get in from a windows machine putty is free and works great.

There is no telnetd, there will be no telnetd.

_________________
cesman

When the source is open, the possibilities are endless!

you realy don't want to be running telnet. SSH is a far better way to go, telnet is not encrypted, so everything is sent clear text. SSh is encrypted, way more secure, just use that, and get putty from above.

if you really, really want telnetd install it at your own risk:
apt-get install telnetd

It's been noted that telnet will never be part of the distribution for Knoppix. I agree, and here is why.

When you log into a session on telnet there are three or four ways of authenticating. However the most common way of doing so is to prompt the user for a username and a password.

In telnet this is done as clear text. Anyone with a way of capturing data on your network will be able to capture your authentication information and pretend to be you for anything that they choose to do.

Additionally users often su to root to do system administration tasks. The user will often get a false sense of security because they do not see the password for the root account being echoed back, but it is still sent in clear text. This is true for any implementation of telnet that is not riding on an ssl or ssh stream.

Configuring telnet to only run across an ssl stream is a bit beyond the scope of a distribution like Knoppix, as is setting up and using a Kerberose server for authentication.

Most of these problems are also true for rsh, though there are a host of other problems there as well.

In any case, the implementation of SSH that is available for Linux provides all of the features most people require of Telnet as well as providing scp capabilities. There are a few other nice capabilities that ssh has which are not available under Telnet, but for most people things such as public key authentication is a bit esoteric.

-Rusty

_________________
Master:
- AMD 1800XP on a MSI KT4V motherboard, via KT400 bios
- 120 G Segate Baracuda /, /cache, /myth, swap
- 200 G Segate Baracuda /myth/tv
- 3 Haupauge! WinTV PVR250s
- 19" Daewoo Monitor (1280x1024 ni)

Hope I can ask a related question w/r/t connecting via SSH...

I've done it no problem via the aforementioned Putty from work. Works great. However, the mythtv password isn't the most secure password out there.

If I login as the mythtv user and change the password, will anything else break? I'm chicken to do it since everything else about my Knoppmyth box is working fantastically.

No.

_________________
cesman

When the source is open, the possibilities are endless!