On Wed, 22 Apr 2020 at 09:23 +0000, you wrote to Tommi Koivula:
BP> possible its just my config, but none have showed what to change in BP> config yet
It may be your build actually. Not sure how you have built your binary, but somehow you disabled MD5 support. Or maybe you are starting binkd with -m option?
=== Start of Windows Clipboard === -m disable CRAM-MD5 authorization === End of Windows Clipboard ===
BP> and none have helped me change gentoo ebuild if its there
You are on your own here. This is free open source software.
BP> i still wonder why enable perl in binkd also enable crypt, so binkd BP> source does not use crupt to have cram-md5 support ?
I have binkd built without perl, and CRAM-MD5 works there. It has nothing to do with crypt library.
=== Start of Windows Clipboard === Binkd 1.0.4 (Aug 24 2014 20:57:51/Win32) Compilation flags: msvc, https, ntlm, amiga_4d_outbound, bwlim. Facilities: rfc2553emu === End of Windows Clipboard ===
BP> if it continues i will enable haproxy, so TLS v1.3 is supported, and BP> remotes will have to use https proxy in there binkd client
This will leave you unreachable via binkp and you will have to remove IBN flag from your nodelist entry.
