D17790: Port away from QCA

[Pino Toscano]

pino added a comment.


  In D17790#382540 <https://phabricator.kde.org/D17790#382540>, @sredman wrote:
  
  > In D17790#382419 <https://phabricator.kde.org/D17790#382419>, @albertvaka wrote:
  >
  > > Using the command line tool means this is a runtime dependency only. You could run kdeconnect without having openssl installed and it would fail mysteriously.
  > >
  > > We can either check that it exists and output a specific error, or change to a compile-time dependency (libopenssl? Not sure if it exists).
  >
  >
  > I'm not sure I'm understanding the conversation. The library is called libssl. It's apparently a little complicated to use, but there is a good StackOverflow example of how it is done: https://stackoverflow.com/questions/256405/programmatically-create-x509-certificate-using-openssl
  
  
  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(). Is the qca-ossl plugin available?

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/3a155227/attachment.html>