On Wed, Apr 15, 2009 at 5:57 AM, Ged gedmurphy@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.