Subj : Re: DoorParty failing??
To   : paulie420
From : Zip
Date : Sat Jul 02 2022 09:24 am

Hello paulie420!

pa> I'm on Debian, yea... and can you imagine - right after sudo apt install
pa> rsh-redone-client, B00M DoorParty fires right up just like normal!!!
pa> Super thank yous for all of your suggestions...

That's great! :)

pa> I wanna grasp what made you think of this - yer saying that you noticed
pa> OpenSSH was handling rlogin? What made you think or find the rsh-redone
pa> package?

I remember trying to use rlogin on my box to connect to Mystic's built-in RLOGIN server, but never getting it to work:

bbs@glimmer:~$ rlogin -vv -p 61513 [email protected]
OpenSSH_8.4p1 Debian-5, OpenSSL 1.1.1n  15 Mar 2022
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolving "scbbs.nsupdate.info" port 61513
debug2: ssh_connect_direct
debug1: Connecting to scbbs.nsupdate.info [188.149.153.205] port 61513.
debug1: Connection established.
debug1: identity file /home/bbs/.ssh/id_rsa type -1
debug1: identity file /home/bbs/.ssh/id_rsa-cert type -1
debug1: identity file /home/bbs/.ssh/id_dsa type -1
debug1: identity file /home/bbs/.ssh/id_dsa-cert type -1
debug1: identity file /home/bbs/.ssh/id_ecdsa type -1
debug1: identity file /home/bbs/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/bbs/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/bbs/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/bbs/.ssh/id_ed25519 type -1
debug1: identity file /home/bbs/.ssh/id_ed25519-cert type -1
debug1: identity file /home/bbs/.ssh/id_ed25519_sk type -1
debug1: identity file /home/bbs/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/bbs/.ssh/id_xmss type -1
debug1: identity file /home/bbs/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.4p1 Debian-5
debug1: kex_exchange_identification: banner line 0: \033[1;1H\033[2J\033[1;1H\033[?1000h\014Mystic BBS Version 1.12 A48
debug1: kex_exchange_identification: banner line 1: Copyright (C) 1997-2022 By James Coyle
debug1: kex_exchange_identification: banner line 2:
debug1: kex_exchange_identification: banner line 3: Detecting terminal emulation: \033[s\033[255BASCII detected.
debug1: kex_exchange_identification: banner line 4:
debug1: kex_exchange_identification: banner line 5: (0) ASCII (no color)
debug1: kex_exchange_identification: banner line 6: (1) ANSI (color)
debug1: kex_exchange_identification: banner line 7:
^C
bbs@glimmer:~$

Apparently it got stuck in the ANSI/ASCII detection for some reason.

When checking the man page for rlogin ('man rlogin'), I noticed that this actually brought up the man page for ssh. When checking what the rlogin command led to, I found:

bbs@glimmer:~$ which rlogin
/usr/bin/rlogin

bbs@glimmer:~$ ls -l /usr/bin/rlogin
lrwxrwxrwx 1 root root 24 aug 11  2018 /usr/bin/rlogin -> /etc/alternatives/rlogin

bbs@glimmer:~$ ls -l /etc/alternatives/rlogin
lrwxrwxrwx 1 root root 15 aug 11  2018 /etc/alternatives/rlogin -> /usr/bin/slogin

bbs@glimmer:~$ ls -l /usr/bin/slogin
lrwxrwxrwx 1 root root 3 mar 13  2021 /usr/bin/slogin -> ssh

So it was a path of links which ended up at the ssh command.

This combined with the fact that the man page didn't mention very much at all
about rlogin made me think that perhaps the rlogin implementation in ssh wasn't working very well.

Then I googled "Debian bullseye rlogin", which brought me to the Debian package search, and there (https://packages.debian.org/search?suite=bullseye&arch=amd64&searchon=contents
&keywords=rlogin) I found out that the rlogin "file" was provided by multiple packages.

One of them was the package "rsh-client", about which it says that also "openssh-client" provides it, i.e. the OpenSSH package (that the ssh command comes with). So that's where rlogin on my system came from.

I thought that installing one of the alternatives (rsh-client or rsh-redone-client) would work -- at least in a different way! -- and apparently "rsh-redone-client" was the newer one of these, so seemed like a good candidate. :-D

And the reason why this would work without changing the commands in the script is that it uses the "alternatives" selection/linking system for choosing the appropriate command (i.e. choosing rlogin from "rsh-redone-client" instead of rlogin from "openssh-client").

pa> Regardless, THANK YOU ZIP!!!! w00t w00t; all of 2o's 'things' are fixed
pa> and working perfectly [ha] on the new server!

Glad to hear that, and glad to be able to help! =)

Best regards
Zip

--- Mystic BBS v1.12 A48 2022/04/26 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.