[nos-bbs] etelnet

n6mef at mefox.org n6mef at mefox.org
Fri Mar 30 22:18:59 EDT 2018


What I'm trying to understand is how it actually works so we can develop a compatible client (for example, in Outpost).  This would be useful for user access over TCP/IP Part 97 radio where the password would otherwise be in the clear.

Based on the archive manual, apparently JNOS includes a challenge in the password prompt.  What happens next is not described.  Evidently, the client reads the challenge, <does something with the challenge and password to compute a response>, and then send the response instead of a plain text password.

I guess I can search for MD5AUTHENTICATION in the code to see if I can decipher what it's doing.


-----Original Message-----
From: nos-bbs <nos-bbs-bounces at tapr.org> On Behalf Of Maiko Langelaar
Sent: Friday, March 30, 2018 2:53 PM
To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
Subject: Re: [nos-bbs] etelnet

Oops, I was actually going to respond to this ...

I've never used it, but this is basically what I tried for the fun of it :

  * Compiled my JNOS with MD5AUTHENTICATION support, figure out how this
    works, okay I see, it's plain TELNET but with MD5 encryption on the
    payload, easy  enough to use, no special service to run, from my own
    command line :

     jnos> etelnet ve4klm <password>

That's about all there was to it, documented in the original JNOS :


but that was there before JNOS 2.0 was even an idea ...


On Thu, 22 Feb 2018, n6mef at mefox.org wrote:

> I had not heard of etelnet before.  A few questions:
>  1. Is it CRAM-MD5 or DIGEST-MD5 or something proprietary?
>  2. Is it just for use in BBS forwarding?  Or could it be used by a client
>     application, such as Outpost, for a user to connect to his/her JNOS
>     mailbox (assuming the client app is enhanced with the same function)?
>  3. If the answer to #2 is “yes”, then where is it documented so we can
>     develop a compatible client?  I see only 1 paragraph in the user manual,
>     which doesn’t provide any details.
> Michael

More information about the nos-bbs mailing list