On 05/01/2014 03:51 PM, Jeremy Lainé wrote:
One problem I am going to run into is that Apple's API doesn't seem to
provide error
details when a certificate check fails (SecTrustEvaluate), so I don't think
we'll get as
fine-grained QSslError's as when using OpenSSL. I have however managed to
Could this be a solution: https://github.com/x2on/OpenSSL-for-iPhone ?
This project provides a script to make a static build of OpenSSL to be used on
iOS 4.3 - iOS 7.1.
Cheers,
Kurt
On 02 May 2014, at 10:16, Jeremy Lainé jeremy.la...@m4x.org wrote:
On 05/01/2014 03:51 PM, Jeremy Lainé wrote:
On Fri, May 2, 2014 at 11:31 AM, Kurt Pattyn pattyn.k...@gmail.com wrote:
Could this be a solution: https://github.com/x2on/OpenSSL-for-iPhone ?
This project provides a script to make a static build of OpenSSL to be used
on iOS 4.3 - iOS 7.1.
Cheers,
Kurt
It works properly when Qt built
On 04/30/2014 11:42 AM, Peter Hartmann wrote:
Yeah, nice work! I think it would be a good thing to get this into qtbase
(should you be
willing to contribute this of course); providing only a subset of the QSsl*
functionality sounds perfectly fine to me...
I have created a qssl-ios branch in
On 29 Apr 2014, at 13:31, Richard Moore r...@kde.org wrote:
On 29 April 2014 12:13, Sorvig Morten morten.sor...@digia.com wrote:
What would the best course of action be to add support for secure
websockets
on iOS?
Probably to add a new QSslSocket backend that uses the Apple
Maybe writing an OpenSSL compatibility layer over Apple's API is also an option?
Does anyone has an idea where OpenSSL is used in Qt? Definitely for SSL
sockets, but maybe also for generating ciphers, hashes, aso?
Cheers,
Kurt
On 29 Apr 2014, at 14:21, Jeremy Lainé jeremy.la...@m4x.org wrote:
Nice work!
I suppose you just want to replace the private implementation of QSSLSocket
leaving the QSSLSocket header intact?
QWebSockets depends further on the OpenSSL macro (can't remember the exact name
now) to decide whether SSL sockets are supported. I think we also need another
macro that
On 04/29/2014 06:36 PM, Jeremy Lainé wrote:
OK I have moved my proof of concept code here:
https://github.com/jlaine/qsslsocketios
(...)
I'll start looking how hard it would be to actually integrate this into
qtbase.
Yeah, nice work! I think it would be a good thing to get this into
qtbase
On 29 Apr 2014, at 00:16, Jeremy Lainé jeremy.la...@m4x.org wrote:
On 04/28/2014 11:44 AM, Nichols Andy wrote:
It is possible still in the packaged versions of Qt for iOS to make
connections using SSL via QNetworkAccessManager as there is a backend that
uses Apples crypto API, but
On 29 Apr 2014, at 00:39, Thiago Macieira thiago.macie...@intel.com wrote:
Em ter 29 abr 2014, às 00:16:43, Jeremy Lainé escreveu:
On 04/28/2014 11:44 AM, Nichols Andy wrote:
It is possible still in the packaged versions of Qt for iOS to make
connections using SSL via QNetworkAccessManager
On 29 April 2014 12:13, Sorvig Morten morten.sor...@digia.com wrote:
What would the best course of action be to add support for secure
websockets
on iOS?
Probably to add a new QSslSocket backend that uses the Apple API.
QSSLSocket/QSslCertificate/QSslCipher is a relatively large API -
On 29 Apr 2014, at 13:31, Richard Moore r...@kde.org wrote:
I actually started thinking about how a smaller API for some of this could
look. Basically with the idea being that for many applications only a subset
of the full QSslXX apis mattered. If you want me to post my notes (such as
On 04/29/2014 02:39 PM, Sorvig Morten wrote:
This aproach looks promising. If we can get basic QSslSocket working (enough
for say QNAM and QWebSocket) then retiring the NSUrlConnection backend and
focusing on QSslSocket is a possibility.
OK I have moved my proof of concept code here:
Hi,
I have installed qt-opensource-mac-x64-ios-5.3.0-beta.dmg
and while compiling my app, I get:
no member named 'sslConfiguration' in 'QNetworkReply'
which is happening when QT_NO_SSL is defined - which seems to be the case
in qconfig.h:
#if defined(QT_NO_OPENSSL) defined(QT_OPENSSL)
# undef
Hi Martin,
I have installed qt-opensource-mac-x64-ios-5.3.0-beta.dmg
and while compiling my app, I get:
no member named 'sslConfiguration' in 'QNetworkReply'
which is happening when QT_NO_SSL is defined - which seems to be the case
in qconfig.h:
#if defined(QT_NO_OPENSSL)
Unfortunately dlopen is not possible :(
Simon
Opprinnelig melding
Fra: Thiago Macieira
Sendt: 18:14 mandag 28. april 2014
Til: development@qt-project.org
Emne: Re: [Development] No SSL on iOS ?
Em seg 28 abr 2014, às 09:44:49, Nichols Andy escreveu:
The packaged (binary) versions of iOS do
Em seg 28 abr 2014, às 09:44:49, Nichols Andy escreveu:
The packaged (binary) versions of iOS do not include support for OpenSSL
because that would require the static linking (and thus distribution) of
OpenSSL which can be problematic due to export restrictions. It is not
possible to build in
On 04/28/2014 11:44 AM, Nichols Andy wrote:
It is possible still in the packaged versions of Qt for iOS to make
connections using SSL via QNetworkAccessManager as there is a backend that
uses Apples crypto API, but without OpenSSL support you can’t use any of the
API’s in Qt that use
Em ter 29 abr 2014, às 00:16:43, Jeremy Lainé escreveu:
On 04/28/2014 11:44 AM, Nichols Andy wrote:
It is possible still in the packaged versions of Qt for iOS to make
connections using SSL via QNetworkAccessManager as there is a backend
that uses Apples crypto API, but without OpenSSL
On 29 Apr 2014 00:39, Thiago Macieira thiago.macie...@intel.com wrote:
Em ter 29 abr 2014, às 00:16:43, Jeremy Lainé escreveu:
What would the best course of action be to add support for secure
websockets
on iOS?
Probably to add a new QSslSocket backend that uses the Apple API.
OK,
20 matches
Mail list logo
