When I come to the point where I am able to build and boot on an image
that contains the packages that I want, be assured that telnetd and ftpd
will soon be a part of it. Using ssh is overkill when working in a safe
and known environment with limited CPU and storage resources, so I bring
it up.
You may have noticed that the mail I sent wasn't just about this issue,
so why did you choose to comment on just this?
Peter
Ian Darwin wrote:
Why does access have to be through ssh? In a secure environment, we
are a couple of guys who are very comfortable with telnet and ftp and
as the resources are still limited, it doesn't seem out of line
(please spare me the paranoia that I often hear when discussing this
with young people, because I am well aware of the potential problems :-)
Please spare us the attitude :-) Use the mini-sshd that is provided.
Developer resources (time) is limited, as you say, and I am quite sure
that the core developers have more important things to do. If you
have the time and energy to compile and build a system with telnetd
and ftpd just so you can use it, go ahead. Otherwise why even bring
it up?
