linuxdcpp-team team mailing list archive

[Razzloss <question107535@xxxxxxxxxxxxxxxxxxxxx>]

Question #107535 on LinuxDC++ changed:
https://answers.launchpad.net/linuxdcpp/+question/107535

    Status: Open => Answered

Razzloss proposed the following answer:
I personally don't have any recommendations for hub software. I haven't
used any other hubsoft than opendchub which I use for testing. And I
haven't really bothered to check anything else. (you probably should not
use opendchub in a 'production' environment).

Note that you should be using unreleased versions of Linuxdcpp (eg.
compile the trunk or use our PPA's with debian based distros). Since the
ADC(s) support isn't fully compatible with the latest ADC standard in
the <0.700 cores which linuxdcpp 1.0.3 uses.

If the problem still occurs with latest linuxdcpp it can be because of a
broken openssl library in either end. At least DSHub used a broken
implementation of SSL which caused problems when connecting with working
OpenSSL with TLS (you had to manually force the SSL3 mode to be able to
connect such DSHubs). So either your linuxdcpp is using broken OpenSSL
or your hub software. With Linuxdcpp you should be able to just upgrade
your openssl packages (no recompilation of linuxdcpp should be needed).
Not sure how uhub works.

--RZ

-- 
You received this question notification because you are a member of
LinuxDC++ Team, which is an answer contact for LinuxDC++.