Hello Michel,

  MS> And now, for the ones who must cope with transitions on their
    > own, euh...  there's more to come: ~WEB~ access (which may go
    > unnoticed by some people but not everyone) and then ~SSH~
    > (idem).  Considering the increasing number of these transitions,
    > i shouldn't be surprized that you must happen to wonder about
    > which it is!

You make it sound as though users are being forced to progress through
dial-up -> Telnet -> Web -> SSH, which is nonsense. Those
technologies are simply alternative means of connecting to a BBS.  None are
compulsory and there is certainly no need to progress through them in any
kind of sequence.

  MS> More than once!  In that case i shall make my posts *LESS*
    > legible!

:-(

  MS> ...then grant ~TelNet~ access only after the ~IP~ address is
    > approved...

  AB> Please explain...  That would not work for the many, many people
    > who are assigned IP addresses dynamically...

  MS> Instead of "like" i should have wrote
"similar" as i wouldn't
    > agree to depend on ~E-Mail~ myself (not before i tried some
    > sturdier methods)!

You missed my point.  Do you suggest that the user is authenticated on the
basis of a static IP address?  Perhaps you meant once each session, but you
have still not explained what mechanisms you would use for authentication
and encryption.

  MS> Indeed, but i haven't tried to determine on which criteria the
    > ~IP~ address should be approved just yet.  What about Domain
    > Names?

What about them.  Do you expect BBS users users to register a domain name
just so that they can connect to a BBS?

  MS> This was only meant as an alternative to accomodate BBSers who
    > must connect using ~SSH~ then ~TelNet~ *SEPARATELY*, for some
    > reason...

What reason?  Describe a scenario in which this makes sense.

  MS> Combining them would accomodate BBSers who can't use file
    > transfers over a same ~SSH~ session but who could ~SSH~ then
    > ~TelNet~, separately.

Any client platform capable of running SSH should also be capable of
running SFTP.  It may also be possible to use traditional BBS file transfer
protocols such as XModem, Kermit etc. over an SSH connection.

- Andy Ball

 * SLMR 2.1a *

--- BBBS/NT v4.01 Flag-5
 # Origin: FamilyNet Sponsored by http://www.christian-wellness.net (8:8/2)