Hello, John! Thank you very much, again 
I conducted a thorough investigation of this problem and found that the problem only occurs on a statically linked DA version 1.51.3 for FreeBSD 9.1. I'm sorry if it looks slightly confusing, my testing server running FreeBSD 10.3, but installed DA binary was
$ ./directadmin -v ; file directadmin
Version: DirectAdmin v.1.51.3
directadmin: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 9.1, not stripped
This error does not occurs at same FreeBSD box with dinamically linked DA for FreeBSD 11. So I think this error is only produced by statically linked binary for FreeBSD 9.x, may be linked against old libssl version, or you just leaved it for backwards compatibility with too old DA versions. I understand it, one of my boxes is FreeBSD 8 - too old, but too much users with productive sites on it and no way to up it to 10 or 11.
So, another questin is follows: can I have a new statically linked binary for FreeBSD 9.х with SSLv2 disabled (because no libc++.so.1 in FreeBSD 9)?
>Also try connecting to your server with a browser (eg: Chrome) to see which protocol the browser is using.
>Chrome is a quick and easy way to do a basic evaluation of the DirectSlaves server's SSL protocols.
Of course I know it ^_^ Better way is to use openssl binary as a s_client.
I'm already done all the tests I can about TLS & SSL support in DS binary and this is strong TLSv12 support. Also, no support for SSLv2 in golang 1.8.
Thank you for all the support, again and again!
Great job, great software, great you! 
DirectAdmin Forums...
ما را در سایت DirectAdmin Forums دنبال میکنید
برچسب: نویسنده: ایمان اصلاحی بازدید: 324 تاريخ: يکشنبه 7 خرداد 1396 ساعت: 4:14