Inetd could be a solution, sure, it really depends on the purpose of coding
this. If you want to learn to use sockets it would be a good idea to write
it all yourself. It really isn't hard at all, especially in Ruby!

Good luck!!

-Mitch

----- Original Message -----
From: "Gil Cohen" <gilc / shoploop.com>
To: "ruby-talk ML" <ruby-talk / ruby-lang.org>
Sent: Wednesday, February 21, 2001 12:32 PM
Subject: [ruby-talk:11248] RE: Telnet/SSH service


> Using a lovely thing called inetd, you don't have to worry about sockets.
It
> does everything for you. Your program talks with whoever telnet'd in via
> stdin/stdout. pretty cool, eh? don't know what to tell you about the ssh
> thing though.
>
>
>
> -----Original Message-----
> From: nosuzuki / e-mail.ne.jp [mailto:nosuzuki / e-mail.ne.jp]On Behalf Of
> Nick Bensema
> Sent: Tuesday, February 20, 2001 6:40 PM
> To: ruby-talk ML; ruby-talk / netlab.co.jp
> Subject: [ruby-talk:11191] Telnet/SSH service
>
>
> I'm among a group of people who are trying to get a simple BBS server up,
> with Telnet.
>
> Unfortunately, using raw sockets doesn't seem to work all that well.
> We can tinker with it to the point where it works with Windows Telnet,
> but most other clients get garbage characters and other such things.
>
> I'd rather work on features like a user list or message board than
> spend a few hours reinventing the wheel.  I'd like to know a couple of
> things:
>
> first, is there a Telnet server module available?  I'm aware of the
> client one, but it doesn't look like it goes both ways.
>
> Second, if I were to get OpenSSL support working, would that be enough
> to talk to ssh clients?
>
> --
> Nick Bensema <nickb / io.com>      ICQ#2135445
> ==== ======= ==============
> BOY, THIS IS REALLY EXPENSIVE!
>
>
>