D17790: Port away from QCA

[Albert Vaca Cintora]

albertvaka added a comment.


  In D17790#387972 <https://phabricator.kde.org/D17790#387972>, @pino wrote:
  
  > Please do **not** use libcrypto/libssl directly:
  >
  > - it does not have a stable ABI
  > - its API changes often too
  > - its license is not exactly nice, imposing extra clauses on what uses it; see https://www.openssl.org/docs/faq.html#LEGAL2 and https://people.gnome.org/~markmc/openssl-and-the-gpl.html (and they will switch soon to Apache 2.0)
  >
  >   To get to the point of this patch: what is the problem it is trying to solve? The linked bug (402323) just mentions a generic failure, when loading a certificate via QSslCertificate::fromPath() on macOS. Was any debugging done to know why?
  
  
  Thanks for the info! We wanted to rid of QCA because it's a rather big library and it gave us some problem with the Windows and Mac ports. We only use it to generate a certificate the first time kdeconnect runs, so any library that can do that would work for us.

REVISION DETAIL
  https://phabricator.kde.org/D17790

To: nicolasfella, #kde_connect
Cc: sredman, albertvaka, pino, apol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20190107/a9c3ae36/attachment.html>