Re: [ros-dev] [ros-diffs] [sedwards] 40485: add telnet service, enable it by default

[Ged]

Why would we want to implement an ssh server?
IMO, telnet and ssh servers are things users should install themselves using
well known products.

I don't know of anyone who uses telnet or ssh in the windows world. They're
unix tools for command line junkies.
We have much cooler tools like RDP.

XP/vista doesn't have these services so I'm not really sure why we do.
They just increase the build time and take up OS resources

Maybe a better option would be to add the kpym.com tools to downloader and
let anyone who may want to install them.

Ged.


-----Original Message-----
From: ros-dev-bounces(a)reactos.org [mailto:[e-mail]] On
Behalf Of Steven Edwards
Sent: 15 April 2009 14:27
To: ReactOS Development List
Subject: Re: [ros-dev] [ros-diffs] [sedwards] 40485: add telnet service,
enable it by default

On Wed, Apr 15, 2009 at 5:57 AM, Ged <gedmurphy(a)gmail.com> wrote:
>   Have you not got your unix head on here?
>  I don't think most windows users even know what a telnet server is for, 
let
>   along help to stress/develop it. 
My hope was that it would help us nail down some of the issues we will
face when we implement or support a proper ssh server. Eventually I
plan on setting telnetd to disabled but given we have no other real
security and anyone using ReactOS on any system with any sort of
critical data is insane I don't see a problem with it. I would in fact
be impressed if someone did manage to make a botnet out of a bunch of
ReactOS boxen. The PR would do us some good.

>   Maybe I'm out of touch here though, if this is
> indeed useful then I 
succumb.

It will be more useful when I fix the remaining console issues so apps
like ctm, tlist, edit, etc work. Stuff like ping, ipconfig, load,
route, etc work. Right now calling Get/SetConsoleMode bombs because it
is parentless and most complex applications expecting to run in
cmd.exe expect to have some sort of real console to set modes. I think
I've found a solution I just need to run it by KJK or get the time to
test it out.

'There is another...' so to speak. I didn't find it until after I had
already started spending a good bit of time working on the current
telnetd implementation.

http://www.kpym.com/2/kpym/index.htm

Its FOSS and does sshd and telnetd and does not seem to suffer from
the console problems we face, however there seems to be some sort of
problem starting or installing the service the last time I tested. I'd
be happy to just dump the current telnetd in favor of it if it can be
made to work under ROS. I just don't want to see what limited remote
access we have now regress which is why i went ahead and enabled it.

-- 
Steven Edwards

"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev