apam,
good evening. I recently upgraded raspian to the latest release and my ssh connections stopped working. I have tried recompiling magicka, and also regenerating the keys, but I still get "key exchange failed" errors. I am guessing that maybe a package got upgraded, or removed, that is necessary.

It does appear that both libssh-dev (0.8.7-1) and libssl-dev (1.1.1c-1) are still installed.

Can you refresh my memory as to which packages need to be installed for the
SSH connections to work?

Thanks!


... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Re: SSH
By: Blue White to Apam on Tue Aug 13 2019 07:39 pm

Can you refresh my memory as to which packages need to be installed for the SSH connections to work?

I'm guessing you're using syncterm or netrunner? Both of which rely on cryptlib. Magicka uses openssl & libssh, and recently it's been made incompatible. You can try MagiTerm or another terminal, but I couldn't convince
libssh to work with out of date crypto to make it compatible with cryptlib.

It's a pain I know. Sorry.

Andrew
--- SBBSecho 3.08-FreeBSD
* Origin: Nocturnal - nocturnal.hopto.org:2023 (21:1/125)

14 Aug 19 14:37, you wrote to Blue White:

cryptlib. Magicka uses openssl & libssh, and recently it's been made incompatible. You can try MagiTerm or another terminal, but I couldn't convince libssh to work with out of date crypto to make it compatible
with cryptlib.

I'm moving my DOS BBS to windows 10 from windows XP. Just wanted to let
you know the new magiterm you hatched is connecting just fine to the openssh server in windows 10 I have configured as a tunell to the BBS.

Syncterm just disconnects without a warning I haven't looked into this
much yet but ass u me it's to do with the above old libraries in syncterm.
Once I get the VM moved over and live I'll post in dovenet and see if anyone there has any ideas.

Shawn


... God is a comedian playing to an audience too afraid to laugh.
--- GoldED+/W32-MINGW 1.1.5-b20160201
* Origin: Tiny's BBS - tinysbbs.com (21:1/130)

Apam wrote to Blue White <=-

I'm guessing you're using syncterm or netrunner? Both of which rely on cryptlib. Magicka uses openssl & libssh, and recently it's been made incompatible. You can try MagiTerm or another terminal, but I couldn't convince
libssh to work with out of date crypto to make it compatible with cryptlib.

It's a pain I know. Sorry.

You are correct, I am using syncterm. It is no big deal to try out
magiterm so I shall do so. Are there any dependencies for compiling it
that I should know about?

Thanks!

P.S. Never mind, I see you have a deb package so I shall try that out first!

... Got my tie caught in the fax... Suddenly I was in L.A.
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Re: Magiterm SSH (Stole thread)
By: Tiny to Apam on Wed Aug 14 2019 02:23 pm

Syncterm just disconnects without a warning I haven't looked into this much yet but ass u me it's to do with the above old libraries in syncterm. Once I get the VM moved over and live I'll post in dovenet and see if anyone there has any ideas.

It might be to do with something NuSkooler discovered a while back that cryptlib doesn't send keep alives.

Andrew
--- SBBSecho 3.08-FreeBSD
* Origin: Nocturnal - nocturnal.hopto.org:2023 (21:1/125)

Quoting Apam to Tiny <=-

It might be to do with something NuSkooler discovered a while back
that cryptlib doesn't send keep alives.

I'm not super worried about it as I figure openssh is pretty much a
standard so if magiterm works with that I'm happy and will just
recomend using magiterm. (I also tested with putty, and the ssh
client built into windows powershell both work)

Shawn

... Diets are for those who are thick and tired of it.

--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

I'm guessing you're using syncterm or netrunner? Both of which rely
on cryptlib. Magicka uses openssl & libssh, and recently it's been
made incompatible. You can try MagiTerm or another terminal, but I
couldn't convince
libssh to work with out of date crypto to make it compatible with cryptlib.

Installed the latest magiterm using the deb package this afternoon. It
seems to work just fine so far! I do have one question. I found two
packages in the amd64 directory. One has dbgsym in the name. I did not install it. I assume that is some sort of debug package? Do I need it?

Thanks!


--- MagickaBBS v0.12alpha (Linux/armv7l)
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Re: RE: SSH
By: Blue White to Apam on Fri Aug 16 2019 04:55 pm

Installed the latest magiterm using the deb package this afternoon. It seems to work just fine so far! I do have one question. I found two packages in the amd64 directory. One has dbgsym in the name. I did not install it. I assume that is some sort of debug package? Do I need it?

Yep, the normal debian package has debuggin symbols stripped (makes the file smaller) I'm gussing the dbgsym package has an executable with debugging symbols.

Andrew
--- SBBSecho 3.08-FreeBSD
* Origin: Nocturnal - nocturnal.hopto.org:2023 (21:1/125)

Hey Apam (and all),

SSH was working perfectly, and then last night I decided to be brave and update ubuntu to the 19.10 version. LOL Now I get key exchange failed on
the MagickaBBS.

Should I just delete the keys and try re-creating them or did I screw something else up?

Also one more stupid question... I grabbed forhonour-c from your gitlab
but it doesn't seem to compile for me. Seems to be an issue with Opendoors.
I couldn't write a hello word in c so I'm lost. ;)

Shawn
P.S. Tomorrow I ask a web site question. So you may want to hide under your desk for that one. LOL
--- Ezycom V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

Also one more stupid question... I grabbed forhonour-c from your
gitlab but it doesn't seem to compile for me. Seems to be an issue with Opendoors. I couldn't write a hello word in c so I'm lost. ;)

I had to take out the...

if [ "$unamestr" == 'Linux' ]; then

Also take out the..

else
gmake
fi

I don't know why but that worked on my linux box.

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hey Apam (and all),

SSH was working perfectly, and then last night I decided to be brave
and update ubuntu to the 19.10 version. LOL Now I get key exchange failed on the MagickaBBS.

What SSH client are you using? If you're using syncterm or Netrunner, it
might be because Ubuntu 19.10 has updated openssl / libssh to something cryptlib can't quote with.

Also one more stupid question... I grabbed forhonour-c from your
gitlab but it doesn't seem to compile for me. Seems to be an issue with Opendoors. I couldn't write a hello word in c so I'm lost. ;)

Try typing "bash ./build.sh" and see if it works.

Andrew

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)

Quoting apam to Tiny <=-

What SSH client are you using? If you're using syncterm or Netrunner,
it might be because Ubuntu 19.10 has updated openssl / libssh to
something cryptlib can't quote with.

Ahhh! Thanks. So I will just ignore this for now. (Just tested and
Magiterm does work - so if anyone asks I'll recomend magiterm)

Try typing "bash ./build.sh" and see if it works.

Got much further thanks. Seems to be an issue with pkg-config search
path for lua-5.3 now. I'll keep on googling away. I'll get it!
Seems ubuntu is not the best distro for this stuff, I was debating
between it and Fedora, but figured ubuntu would be easier.

Shawn

... We are going to have peace even if we have to fight for it.

--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

Ti> Ahhh! Thanks. So I will just ignore this for now. (Just tested
and

Magiterm does work - so if anyone asks I'll recomend magiterm)

I'm really hoping cryptlib is updated soon so syncterm / netrunner work.
A lot of people use those clients, and magiterm isn't exactly
spectacular - it still has problems with ZModem :(

Got much further thanks. Seems to be an issue with pkg-config search
path for lua-5.3 now. I'll keep on googling away. I'll get it!

You might need to install the lua development package: liblua5.3-dev

Seems ubuntu is not the best distro for this stuff, I was debating
between it and Fedora, but figured ubuntu would be easier.

You're probably better off with ubuntu, not because it's better than
fedora (they're both ok distros), but as it's based on debian everything
in the documents for magicka should work as is. Fedora uses different
package names for things.

I use opensuse on the desktop and had to write a special build.sh for for-honour because it installs lua-5.3 as lua5.3 (no dash) so the
current script fails.

Andrew

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)

25 Oct 19 22:04, you wrote to me:

I'm really hoping cryptlib is updated soon so syncterm / netrunner
work. A lot of people use those clients, and magiterm isn't
exactly spectacular - it still has problems with ZModem :(

That's true, I forgot about that as I have been using syncterm out of
habit for grabbing the bluewave packets.

You might need to install the lua development package: liblua5.3-dev

Sigh, you are correct. It compiled now. LOL

I use opensuse on the desktop and had to write a special build.sh for for-honour because it installs lua-5.3 as lua5.3 (no dash) so the
current script fails.

Ahhh okay sounds like in the end it may be the right choice. Once I
bug you for help a few dozen times it's fine after that, it's just a matter
of getting the right dev tool sinstalled and then it's smooth.

Shawn


... Marriage is a great institution - no family should be without it.
--- GoldED+/W32-MINGW 1.1.5-b20160201
* Origin: Tiny's BBS - tinysbbs.com (21:1/130)

25 Oct 19 22:04, you wrote to me:

You might need to install the lua development package: liblua5.3-dev

Strange one now... the LUA scripts built into the menus, forhonour, work,
as well as the last caller one that just writes to the jam base. But none of the
scripts that interact with the user do anything.

ie: Global last callers, the One linerz etc.

That stopped working before you came back to developing, did you fix that yet or is it still broken / something on this end? If it's still broken I'm just going to remove the options from the menus and not worry about it.

Shawn
P.S. Got the two pesky dos doors working I was fighting with! Good day. LOL


... Sometimes a man will tell his bartender things he'll never tell his doctor --- GoldED+/W32-MINGW 1.1.5-b20160201
* Origin: Tiny's BBS - tinysbbs.com (21:1/130)

P.S. Got the two pesky dos doors working I was fighting with! Good day. LOL

I've been toying with the idea of running a couple of dos doors. I went
into aptitude to look up dosemu and it's not there anymore, or if it is I couldn't find it.

What are folks using to run dos doors these days?

I wonder if dosemu is in debian 8 or 9 and if that would work?

Ttyl :-)
Al

--- MagickaBBS v0.13alpha (Linux/x86_64)
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Quoting Al to Tiny <=-

I wonder if dosemu is in debian 8 or 9 and if that would work?

I'm no linux expert. On ubuntu 19.10 I just did "apt-get install
dosemu" and followed the instructions on the magickaBBS wiki for dos
doors.

They seem to work pretty good so far!

Shawn

... My IQ test came back negative.

--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)