For some reason, when connecting to my Ubuntu 22.04 SSHD, it fails the ansi detection and when entering text, that text isn't displayed until I hit
enter. This is under a VMWare Workstation Pro Guest with a Windows 10 Pro Host. I'm logging on with a key, not password. I've tried both.

I tried upgrading it with no success.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

Hello Shurato,

Friday August 02 2024 21:58, you wrote to All:

For some reason, when connecting to my Ubuntu 22.04 SSHD, it fails the
ansi detection and when entering text, that text isn't displayed until
I hit enter. This is under a VMWare Workstation Pro Guest with a
Windows 10 Pro Host. I'm logging on with a key, not password. I've
tried both.

You will not get ANSI over a ssh connection normally until you log into the BBS proper. You will also not see your password echoed in ssh if you are using one but it sounds like your sshd config is wrong.

-- Sean

... "Tale-bearers are as bad as tale-makers." - Sheridan
--- GoldED/2 3.0.1
* Origin: Outpost BBS, Johnson City, TN / bbs.outpostbbs.net:10323 (618:618/1)

* In a message originally to Shurato, Sean Dennis said:

Hello Shurato,

Friday August 02 2024 21:58, you wrote to All:

For some reason, when connecting to my Ubuntu 22.04 SSHD, it fails the ansi detection and when entering text, that text isn't displayed until
I hit enter. This is under a VMWare Workstation Pro Guest with a Windows 10 Pro Host. I'm logging on with a key, not password. I've tried both.

You will not get ANSI over a ssh connection normally until you log into
the BBS proper. You will also not see your password echoed in ssh if you are using one but it sounds like your sshd config is wrong.

ANSI is detected by the telnet connection, not SSH. Username (or any other text that should be echoed) is not being echoed in telnet through sshd, I'm using telnet -E 192.168.0.7 in the forcecommand. This worked under Debian,
I'm not sure what I'm doing wrong; I'm using the same configuration
changes as near as I can tell. I can supply my sshd_config if you think that would help.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

* In a message originally to Shurato, Sean Dennis said:

Hello Shurato,

Friday August 02 2024 21:58, you wrote to All:

For some reason, when connecting to my Ubuntu 22.04 SSHD, it fails

the

ansi detection and when entering text, that text isn't displayed

until

I hit enter. This is under a VMWare Workstation Pro Guest with a Windows 10 Pro Host. I'm logging on with a key, not password.

I've

tried both.

You will not get ANSI over a ssh connection normally until you log into the BBS proper. You will also not see your password echoed in ssh if

you

are using one but it sounds like your sshd config is wrong.

ANSI is detected by the telnet connection, not SSH. Username (or any other text that should be echoed) is not being echoed in telnet
through sshd, I'm using telnet -E 192.168.0.7 in the forcecommand.
This worked under Debian, I'm not sure what I'm doing wrong; I'm
using the same configuration changes as near as I can tell. I can
supply my sshd_config if you think that would help.

If I ssh into my Ubuntu VM and then telnet to the BBS it works fine. It's
just using "ForceCommand telnet -E 192.168.0.7" that is causing the problem.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)


Hello Shurato!

06 Aug 24 18:35, you wrote to me:

ANSI is detected by the telnet connection, not SSH. Username (or any other text that should be echoed) is not being echoed in telnet
through sshd, I'm using telnet -E 192.168.0.7 in the forcecommand.
This worked under Debian, I'm not sure what I'm doing wrong; I'm using
the same configuration changes as near as I can tell. I can supply my sshd_config if you think that would help.

Is your telnet running in 'linemode' or 'single character' mode?

From "man telnet":

"

-- Sean


... Teamwork is essential; it gives the enemy other people to shoot at.
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

Hello Shurato!

06 Aug 24 18:51, you wrote to you:

If I ssh into my Ubuntu VM and then telnet to the BBS it works fine.
It's just using "ForceCommand telnet -E 192.168.0.7" that is causing
the problem.

Try putting the telnet command in a script. Note this is shown using ssh keys, and not u/p style.

This should help: https://shaner.life/the-little-known-ssh-forcecommand/

-- Sean


... Wynne's Law: negative slack tends to increase.
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

↑↑
Hello Shurato!

06 Aug 24 18:35, you wrote to me:

ANSI is detected by the telnet connection, not SSH. Username (or any other text that should be echoed) is not being echoed in telnet through sshd, I'm using telnet -E 192.168.0.7 in the forcecommand. This worked under Debian, I'm not sure what I'm doing wrong; I'm

using

the same configuration changes as near as I can tell. I can supply

my

sshd_config if you think that would help.

Is your telnet running in 'linemode' or 'single character' mode?

I don't know, I'm just running "telnet" with parameters. I looked at the manpage and couldn't figure out how to preset it in either mode; only via a mode command and using -E I can't get to the commands. I tried your
suggestion of using a script from ForceCommand, but that didn't make a difference. If I run telnet from the command line, it works just fine as I stated. It's only from ForceCommand that it doesn't appear to work any more. This worked fine from Debian, but I switched to Ubuntu.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

Hello Shurato!

06 Aug 24 18:51, you wrote to you:

If I ssh into my Ubuntu VM and then telnet to the BBS it works fine. It's just using "ForceCommand telnet -E 192.168.0.7" that is causing the problem.

Try putting the telnet command in a script. Note this is shown using ssh keys, and not u/p style.

That worked! Originally I thought it didn't, but I had forgotten to restart the sshd. Thanks!

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)

ANSI is detected by the telnet connection, not SSH. Username (or any
other
text that should be echoed) is not being echoed in telnet through
sshd, I'm
using telnet -E 192.168.0.7 in the forcecommand. This worked under
Debian,
I'm not sure what I'm doing wrong; I'm using the same configuration
changes as near as I can tell. I can supply my sshd_config if you
think that
would help.

My recollection is that you are using DOS bbs software, right?

Here, with my DOS BBS software, GT Power, most telnet callers need to
call here using a connection type of "RAW" instead of "telnet" to prevent
some odd issues like you are describing.

I do not use SSHD with the DOS BBS at all as I expect that bad things
will happen. If you want to offer SSH connections, you will probably
want to look at using mystic or synchronet as a front-end for the DOS BBS
and allow them to handle the SSH bits.

It sounds like you did have it working under debian, but it doesn't work
with ubuntu. My experience with both is that a lot of things that work
just fine with debian proper don't work with ubuntu, even though it is a
fork of debian. ubuntu likes to stay on the leading edge and, IMHO, the software is not always tested as well as debian stable. It is also much
more difficult for a stable system to be the result of a dist-upgrade
under ubuntu.

Is there a reason you changed from debian to ubuntu?


--- Talisman v0.53-dev (Linux/armv7l)
* Origin: possumso.fsxnet.nz * telnet:24/ssh:2122/ftelnet:80 (618:250/10)

That worked! Originally I thought it didn't, but I had forgotten to restart the sshd. Thanks!

Sure thing. Glad you were able to get it working.

-- <8D~




--- MBSE BBS v1.1.0 (Linux-x86_64)
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

ANSI is detected by the telnet connection, not SSH. Username (or any other text that should be echoed) is not being echoed in telnet
through sshd, I'm using telnet -E 192.168.0.7 in the forcecommand.
This worked under Debian, I'm not sure what I'm doing wrong; I'm
using the same configuration changes as near as I can tell. I can
supply my sshd_config if you think that would help.

My recollection is that you are using DOS bbs software, right?

Win32. EleBBS.

Here, with my DOS BBS software, GT Power, most telnet callers need to
call here using a connection type of "RAW" instead of "telnet" to prevent some odd issues like you are describing.

I do not use SSHD with the DOS BBS at all as I expect that bad things
will happen. If you want to offer SSH connections, you will probably
want to look at using mystic or synchronet as a front-end for the DOS BBS and allow them to handle the SSH bits.

It sounds like you did have it working under debian, but it doesn't work with ubuntu. My experience with both is that a lot of things that work just fine with debian proper don't work with ubuntu, even though it is a fork of debian. ubuntu likes to stay on the leading edge and, IMHO, the software is not always tested as well as debian stable. It is also much more difficult for a stable system to be the result of a dist-upgrade under ubuntu.

Is there a reason you changed from debian to ubuntu?

I thought it would be easier on me. After starting the telnet session from a script file instead of ForceCommand, it's now working. There are some
oddities with ssh connections, like occasionally the files areas don't work, but for the most part it's functional. I encourage Secure Websocket connections if people are worried about telnet security.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (618:300/50)