[nos-bbs] Fwd: Outpost telnet into JNOS

[George [ham] VerDuin]

I can venture a guess Bill.

On 10/23/2009 06:58 PM, Bill V WA7NWP wrote:
> Somebody here on nos-bbs may have some insight.  Could these be the
> telnet negotiation control codes?
>    
Probably not - more likely terminal control.
> Bill - WA7NWP
>
> ---------- Forwarded message ----------
> From: Paul Malarik<malarik at altelco.net>
> Date: Fri, Oct 23, 2009 at 3:52 PM
> Subject: [OutpostPacket] Outpost telnet into JNOS
> To: OutpostPacket at yahoogroups.com
>
>
>
> Hello;
>
> Am evaluating Outpost lan telnet capabilities into JNOS. Outpost can't
> login to JNOS, in this test configuration(LAN only, no RF), Outpost sees
> special characters at the Password prompt which I believe are
> interfering with login. These special characters are viewed in the
> Packet Interactive Session. And are pasted below(however the process of
> copying changes the special characters form a square root followed by a
> smiley face to what you see below):
> ----------------------------------------------------------
> Connecting by Telnet to Host 10.0.0.101...
> JNOS (n8umo)
>
> login: n8umo
> Password: ÿû test
> ÿü
>    
The PWD text above appears to contain "yu " non-ascii characters twice 
from jnos, perhaps to toggle echo display on the terminal, along with 
the pwd "test<cr><lf>".
I suggest you display the subject characters in HEX then consult the 
documentation for the terminal type emulated by Outpost and compare it 
with (?) emulation you normally use.  This should allow you to discover 
the intended display for comparison to actual display you see.
*If* Outpost automatic login feature is built using the standard 
challenge-response pairs of text, then the extra characters "should not" 
defeat a jnos telnet login by Outpost.

The standard display for pwd is null [not "0" null ascii character, just 
no display at all].
I don't have the source immediately available to see how the echo is 
handled for sure.
The real stretch [ancient memory probe] is DOS -- I seem to remember 
"blank" was displayed for any non-ascii character in a text string.

Passwording for JNOS telnet is particularly weak -- typically clear text.
Jnos has one feature you might use to your advantage:
New user passwords are cataloged just like presented on the initial user 
login.
So if an encrypted pwd is presented for the first login, it may work 
again so long as the process is repeated.
> [JNOS-2.0f-BFHIM$]
> You have 1 message - 1 new.
> Area: n8umo (#1)>
> ----------------------------------------------------------
> These special characters are not seen in a DOS window telnet session.
>
> Anyone have an idea what is happening here or how to correct?
>
> Paul N8UMO
>
> _
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>