Hi Torsten!
17 Dec 2016 00:47, from Torsten Bamberg -> Richard Menedetter:
RM>> I have compiled binkd myself.
RM>> Strangely it does not send the CRYPT option ...
RM>> did I miss a configure flag that I need to set??
TB> Well, possibly you didn't link all files into binkp.
TB> The crypt option is hardcoded. Just take a look at crypt.c.
Hmm ...
It links with -lcrypt ... and I thought it is not sending the CRYPT option, but
the LOG from your side shows that I am sending it to you.
I am not sending it to OpenXP when I poll my sysop point:
To: NETCALL (All)
From: Richard Menedetter @ 2:310/31.1 (fido.ricsi.priv.at, Vienna A)
Subject: Netcall to 2:310/31
Date: Sa 17.12.16, 04:08
Size: 509 Bytes
-------------------------------------------------------------------------------
----------------
= 04:08:13 CONNECT
04:08:13 OPT CRAM-MD5-a24e327d4abfb5f5982c181d162c3bee
04:08:13 SYS fido.ricsi.priv.at
04:08:13 ZYZ Richard Menedetter
04:08:13 LOC Vienna,Austria
04:08:13 NDL 115200,TCP,BINKP,XW,CM,MO,IBN,INA:fido.ricsi.priv.at
04:08:13 TIME Sat, 17 Dec 2016 04:08:26 +0100
04:08:13 VER binkd/1.1a-75/Linux binkp/1.1
04:08:13 TRF 0 0
04:08:13 OPT EXTCMD GZ BZ2
04:08:13 secure
= 04:08:13 hangup
- 04:08:13 exiting
No clue why.
TB> The options inside the makefile are to use the compression.
TB> To use the compression makefile flags you need to have zlib and/or
TB> bzip lib installed and compiled correctly.
I have BZ2, ZLIB and Perl active.
TB> BTW: binkd is actually at version binkd1.1a-95.
TB> binkd1.1a-75 is outdated. ;-)
I know ... I will migrate the fido system to this virtual server:
root@vserv:~# binkd -vv
Binkd 1.1a-94 (Dec 8 2016 11:29:32/Linux)
Compilation flags: gcc, zlib, bzlib2, perl.
Facilities: fts5004 ipv6
Just did not have time/motivation to do so.
TB> If you want me to test your version, just switch binkd (you compiled
TB> by your own) to a different port. Maybe port 25554, and I'll start
TB> connecting to your test binkd as well.
Strangely it seems that I already send the option to you.
So I am sure the "other" binkd on the new vserver is OK as well.
So all is fine.
I just do not get why I am not sending the crypt option to sessions with my
sysop point.
Anyways thanx for the answers.
I will check once more after I migrated, but I assume all is fine ...
CU, Ricsi
--- GoldED+/LNX
* Origin: Hardware Independent: Won't work on ANY hardware! (2:310/31)
|