linuxdcpp-team team mailing list archive

[poy <1620106@xxxxxxxxxxxxxxxxxx>]

I would prefer caution as well, especially as:
- the build process has changed quite a bit;
- there are API changes;
- threading management has evolved - the method used is great in general but scary to use in mingw, where it is quite experimental (though it can be disabled):

  *) OpenSSL now uses a new threading API. It is no longer necessary to
     set locking callbacks to use OpenSSL in a multi-threaded environment. There
     are two supported threading models: pthreads and windows threads. It is
     also possible to configure OpenSSL at compile time for "no-threads". The
     old threading API should no longer be used. The functions have been
     replaced with "no-op" compatibility macros.
     [Alessandro Ghedini, Matt Caswell]

Nevertheless, I'm going to put my build script changes in a branch - got
MinGW versions but can't build VS ones yet.

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/1620106

Title:
  Upgrade to OpenSSL 1.1.0

Status in DC++:
  Won't Fix

Bug description:
  https://www.openssl.org/news/changelog.html#x1 notes:
    *) Support for ChaCha20 and Poly1305 added to libcrypto and libssl.
       [Andy Polyakov]

    *) CCM support via EVP. Interface is very similar to GCM case except we
       must supply all data in one chunk (i.e. no update, final) and the
       message length must be supplied if AAD is used. Add algorithm test
       support.
       [Steve Henson]

  Which are useful to have going forward, and to be useful, to get in as
  early a version as feasible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/1620106/+subscriptions