|
Grex > Garage > #23: Telnetd removal from OpenBSD >= 3.8 and grex. | |
|
| Author |
Message |
cross
|
|
Telnetd removal from OpenBSD >= 3.8 and grex.
| 
Dec 19 14:13 UTC 2005 |
The new version of OpenBSD (version 3.8 and, presumably, future
releases) have removed the telnet daemon from the distribution.
However, a number of grex users use telnet to connect to grex.
I'd like to see more information about how grex is dealing with
this basic OS change. Now, it's not terribly hard to just copy
the telnet source code from an older version of OpenBSD, but that's
a step that shouldn't be neglected, and yet there's no mention at
all of this change in grexdoc. So what's up with it?
|
| 57 responses total. |
nharmon
|
|
response 1 of 57:
|
Dec 19 15:48 UTC 2005 |
The first of Grex's "Security Goals" is "Protecting the privacy of
users." Eliminating Telnet access would certainly be a part of this goal.
|
rcurl
|
|
response 2 of 57:
|
Dec 19 18:39 UTC 2005 |
Does eliminated telnet including eliminating similar daemons, like SSH?
CAEN eliminated telnet some months back, but SSH is the replacement.
|
nharmon
|
|
response 3 of 57:
|
Dec 19 19:09 UTC 2005 |
I don't think eliminating telnet would mean eliminating SSH, since SSH
meets Grex's security goals.
|
bhoward
|
|
response 4 of 57:
|
Dec 19 23:47 UTC 2005 |
Integrating the telnet sources we used is on my short list. It is
blocked pending some answers to questions I've raised regarding
grexsoft and its reintegration with grexdoc.
We've made good progress since the upgrade cleaning up various loose
ends that never made it into or were not kept updated in grexdoc. I'd
love to finish off telnetd and grexsoft ASAP.
As for the other question, whether to retire telnetd entirely...I'd
be very happy to do that but it won't fly unless we write up some
very easy-to-understand instructionas for newusers on how to install
and configure PuTTY (or its moral equivalent). Restricting network
logins to ssh may raise the technical bar too high for some of our
newusers without decent documentation.
|
gull
|
|
response 5 of 57:
|
Dec 21 02:58 UTC 2005 |
I would say either keep telnet around, or find a good SSH Java
application and put it on the web page.
|