Do i need a licence for OpenSSL when doing https requests in Qt??
-
In an application where request is sent over https and self-signed certificates is used, is there any need for a licence for OpenSSL?
From documentation (Qt Network):
"Qt Network can use the OpenSSL Toolkit as a backend. The
library is then linked against OpenSSL in a way that requires
compliance with the OpenSSL License." -
In an application where request is sent over https and self-signed certificates is used, is there any need for a licence for OpenSSL?
From documentation (Qt Network):
"Qt Network can use the OpenSSL Toolkit as a backend. The
library is then linked against OpenSSL in a way that requires
compliance with the OpenSSL License."@Kompa said in Do i need a licence for OpenSSL when doing https requests in Qt??:
is there any need for a licence for OpenSSL?
What license do you mean? There is no commercial license for OpenSSL. You have to make sure you do not violate the OpenSSL license, see https://www.openssl.org/source/license.html
-
@Kompa said in Do i need a licence for OpenSSL when doing https requests in Qt??:
is there any need for a licence for OpenSSL?
What license do you mean? There is no commercial license for OpenSSL. You have to make sure you do not violate the OpenSSL license, see https://www.openssl.org/source/license.html
-
@jsulm
Perhaps the question should have been phrased a little differently:
When I do https requests in Qt do I have to watch out for license restrictions from OpenSSL?@Kompa said in Do i need a licence for OpenSSL when doing https requests in Qt??:
do I have to watch out for license restrictions from OpenSSL?
Yes, I think so. But I'm not a lawyer. You will need to mention the OpenSSL license somewhere in your app as far as I know.
-
@Kompa said in Do i need a licence for OpenSSL when doing https requests in Qt??:
do I have to watch out for license restrictions from OpenSSL?
Yes, I think so. But I'm not a lawyer. You will need to mention the OpenSSL license somewhere in your app as far as I know.
-
@jsulm Thank you! Do you know if the using only http and ignoring all ssl errors will remove the need to mention the OpenSSL license?
@Kompa I would say this depends whether your application uses any parts of Qt which use OpenSSL (and it does since you're doing networking). It doesn't metter whether you only access http or not. What matters is what your app depends on.
-
I would say as soon as you link against OpenSSL and thus ship it with your application you would have to comply with the OpenSSL license. If you don't want to think about this you'd need a Qt version that does not link against OpenSSL (may compile it yourself). I don't think a license only applies if you actually call a function from that library. (But I'm not a lawyer.)
Solely relying only on http is going to be difficult. This will only work for software you write for yourself on both ends. Most webservers will only allow https connections and even browser are moving in that direction. Not using a secure connection will hinder interoperability in the future.
-
K Kompa deleted this topic on
-
K Kompa restored this topic on
