Text 606, 45 rader
Skriven 2004-09-02 12:43:52 av mark lewis (1:3634/12)
    Kommentar till text 573 av Andy Alt (1:14/250)
Ärende: secure pipe
===================
 AA>> I'm sure there are tons of people who would want to get the
 AA>> basics down of how to telnet into a BBS and use it; most
 AA>> people I speak with have never even heard the term BBS.

 ML>> this is true... it was true back in the heyday, too... as for telnet,
 ML>> it really is going by the wayside due to the lack of security...
 ML>> everything in the telnet stream flows plain jane... with today's
 ML>> internet and all the rogues out there, one should almost be using a
 ML>> secure pipe for everything they do...

 AA> I was wondering about security actually. I know as far as
 AA> like, remote administration over systems, people have
 AA> switched to SSH for that because of the security issues. I
 AA> have wondered about the security of the BBS'es themselves
 AA> running thru telnet. I wasn't sure if telnet itself was the
 AA> issue, or the telnet server daemon. You pretty much answered
 AA> that.

and just to ensure that the proper answer got thru, the main issue is that
unless it is encrypted, everything travels in the clear and can be read by
anyone looking in on the passing stream... on POTS lines, this wasn't all that
much of a bother because the line was (rather) secure... but on the 'net, where
everything runs together, it is of concern... the main concern being the
passing of passwords... as far as our BBS' are concerned, there's no real need
to secure the entire link as the content we serve is mostly not secret,
classified, or otherwise restricted...

 AA> I don't know anything about secure pipes. Is that done on
 AA> the server side, or something the client would have to do
 AA> upon telnetting to a BBS?

they have to be set up on both sides of the connection... the server runs the
server and has a copy of the remote users' keys... the remote user uses their
client which uses their key for authentication to the server... the actual keys
don't travel the wire... its all done with what's known as "shared secret"
which would be your password... each side uses the password/secret and runs the
exchange thru a formula... the answers must match what they already know...
secure pipes go even further by encrypting the entire connection stream...

FWIW: shared secret logons were done on BBS' many years back just as the 'net
was becoming more and more popular... its actually pretty darned simple...

)\/(ark

 * Origin: (1:3634/12)