Michael R. Bright wrote: > I must have some serious issues. I looked at the Openssl that I have on my > machine, and it is the most current version. I have seen that the > telnet.pem file doesn't exist. I have tried making a certificate with > the -req command but that doesn't exist either. I am running knoppix. > Would you have any other suggestions, is there something I am missing? > Thanks for the help.
You need to generate both a private key and a certificate for the telnet daemon using openssl. Since I doubt you're going to want to spend the hundreds of dollars to get a cert signed by an "official" CA (since there really is only one: Verisign), you're going to have to make a self-signed cert. Do this as root: dd if=/dev/urandom of=rand.dat bs=1k count=1 openssl genrsa 1024 -rand rand.dat > telnetd.key openssl req -new -x509 -key telnetd.key > telnetd.crt Now telnetd expects to find both the key and the cert in the same file, so do: cat telnetd.key telnetd.crt > telnetd.pem Telnetd should be happy then. However, SSH is far more capable than telnet, it's available for every single OS, and it's secure. Using telnet -- even just having telnetd open -- screams "come hack me." Knoppix has sshd on it. Why on earth do you *not* want to use SSH? -- Soren Harward [EMAIL PROTECTED] ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
