Subj : Re: DoorParty failing??
To   : Zip
From : paulie420
Date : Sat Jul 02 2022 07:00:36

 Zi> I remember trying to use rlogin on my box to connect to Mystic's built-in
 Zi> RLOGIN server, but never getting it to work:
 Zi> debug1: kex_exchange_identification:
 Zi> 
 Zi> Apparently it got stuck in the ANSI/ASCII detection for some reason.
 Zi> 
 Zi> bbs@glimmer:~$ ls -l /usr/bin/slogin
 Zi> lrwxrwxrwx 1 root root 3 mar 13  2021 /usr/bin/slogin -> ssh
 Zi> 
 Zi> So it was a path of links which ended up at the ssh command.
 Zi> 
 Zi> Then I googled "Debian bullseye rlogin", which brought me to the Debian
 Zi> package search, and there I found out that the rlogin "file" was provided  Zi> by multiple packages.
 Zi> 
 Zi> One of them was the package "rsh-client"
 Zi> 
 Zi> I thought that installing one of the alternatives (rsh-client or
 Zi> rsh-redone-client) would work -- at least in a different way! -- and
 Zi> apparently "rsh-redone-client" was the newer one of these, so seemed
 Zi> like a good candidate. :-D
 Zi> 
 Zi> And the reason why this would work without changing the commands in the
 Zi> script is that it uses the "alternatives" selection/linking system for
 Zi> choosing the appropriate command (i.e. choosing rlogin from
 Zi> "rsh-redone-client" instead of rlogin from "openssh-client").

And b00m, now I know exactly why Debian's rlogin was throwing an error I couldn't figure out. Appeciate the explanation even more than the fix - I think I'd of been tied up over this for a lot longer w/o the help. 

It takes a village...

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

:P Very much. Thanks again, kind sir.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A48 2022/04/26 (Linux/64)
 * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

.