• Registered: 2018-08-04
  • Posts: 12

Topic: Unable to connect to pro.beatport.com host

Hello,

When I try to connect to pro.beatport.com host using Wolfssl folowing error is received:

wolfSSL_connect error -313, revcd alert fatal error
wolfSSL error: wolfSSL_connect failed

How to reproduce:

git clone https://github.com/wolfSSL/wolfssl.git
cd wolfssl
./autogen.sh
./configure  --enable-all
make

examples/client/.libs/client -S pro.beatport.com  -h pro.beatport.com  -p 443 -d -x -C -g -i -v d

Could you please help?

Best Regards,
SamSam

Share

  • From: Bozeman
  • Registered: 2014-05-09
  • Posts: 777

Re: Unable to connect to pro.beatport.com host

Hi SamSam,

That domain only supports static RSA cipher suites which wolfSSL disables by default because they are not considered as safe as Perfect Forward Secrecy provided by DHE or ECDHE cipher suites.

Please try this test instead:

git clone https://github.com/wolfSSL/wolfssl.git
cd wolfssl
./autogen.sh
./configure  --enable-all CFLAGS=-DWOLFSSL_STATIC_RSA
make

examples/client/.libs/client -S pro.beatport.com  -h pro.beatport.com  -p 443 -d -x -C -g -i -v d

Let me know your results.


Warm Regards,

Kaleb

Kaleb J. Himes's Website

Share

  • Registered: 2018-08-04
  • Posts: 12

Re: Unable to connect to pro.beatport.com host

Hello,

Yes it works. Thank you very much.
However I had two compilation errors:

CC     wolfcrypt/src/src_libwolfssl_la-asn.lo
wolfcrypt/src/asn.c: In function 'GetAsnTimeString':
wolfcrypt/src/asn.c:4978:31: error: declaration of 'min' shadows a global declaration [-Werror=shadow]
./wolfcrypt/src/misc.c:241:29: error: shadowed declaration is here [-Werror=shadow]
cc1: all warnings being treated as errors  CC     wolfcrypt/src/src_libwolfssl_la-coding.lo

tests/api.c: In function ‘test_wolfSSL_ASN1_TIME_adj’:
tests/api.c:18689:20: error: integer overflow in expression [-Werror=overflow]
cc1: all warnings being treated as errors
make[1]: *** [tests/tests_unit_test-api.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `/tmp/t/wolfssl'
make: *** [all] Error

The first one was easy to fix by changing variable name from "min" to "mins".
The second one I simple commented. But as I understand there is problem with time_t overflow.

What will be the proper fix?

Best Regards,
SSS

Share

  • From: Bozeman
  • Registered: 2014-05-09
  • Posts: 777

Re: Unable to connect to pro.beatport.com host

SamSam,

Can you tell me what system your are building on, architecture and compiler version you are working with? We'd like to reproduce this on our end for implementing a fix. Thanks!

Kaleb J. Himes's Website

Share

  • Registered: 2018-08-04
  • Posts: 12

Re: Unable to connect to pro.beatport.com host

I think  you ask about this information:

$ uname -a
Linux ubuntu-VirtualBox 3.2.0-24-generic-pae #39-Ubuntu SMP Mon May 21 18:54:21 UTC 2012 i686 i686 i386 GNU/Linux

$ gcc -###
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.6/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.3-1ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)

Please let me know if you need anything more.

Best Regards,
SSS

Share

  • From: Bozeman
  • Registered: 2014-05-09
  • Posts: 777

Re: Unable to connect to pro.beatport.com host

Hi SamSam,

I was unable to reproduce this. Can you tell me which version of wolfSSL you are testing with? (I tested with wolfssl-3.15.5, our latest stable release).

Regards,

- K

Kaleb J. Himes's Website

Share

  • Registered: 2018-08-04
  • Posts: 12

Re: Unable to connect to pro.beatport.com host

Hello,

I used head. The information about this was in the first post:

git clone https://github.com/wolfSSL/wolfssl.git
cd wolfssl
./autogen.sh
./configure  --enable-all
make

Regards,
SSS

Share