Re: [Development] RFC: Managing the Addition of New SSL Backends

2014-05-06 Thread Peter Hartmann
Hello, TL;DR: I think we can accept new backends if they support some minmal client-side API, i.e. they succeed connecting when there are no errors and fail if something goes wrong. The big problem IMO is how to advertise to the developer what parts of the API are supported and what not. Some

Re: [Development] RFC: Managing the Addition of New SSL Backends

2014-05-05 Thread Oliver Wolff
On 06/05/2014 08:11, Jeremy Lainé wrote: > Thanks Richard for taking the time to write up your summary, as the subject > is pretty vast. > > On 05/03/2014 11:23 PM, Richard Moore wrote: >> Support for QNAM >> >> >> It's obvious that to be useful, a backend must allow QNAM to make

Re: [Development] RFC: Managing the Addition of New SSL Backends

2014-05-05 Thread Jeremy Lainé
Thanks Richard for taking the time to write up your summary, as the subject is pretty vast. On 05/03/2014 11:23 PM, Richard Moore wrote: > Support for QNAM > > > It's obvious that to be useful, a backend must allow QNAM to make SSL > requests. It need not support the more advance

Re: [Development] RFC: Managing the Addition of New SSL Backends

2014-05-04 Thread Richard Moore
On 3 May 2014 22:38, Thiago Macieira wrote: > Em sáb 03 maio 2014, às 22:23:30, Richard Moore escreveu: > > - A small but significant number of apps use client certificates. > > > > - A small but significant number of apps use server SSL sockets. > > > > - Very few applications use custom trust s

Re: [Development] RFC: Managing the Addition of New SSL Backends

2014-05-04 Thread Richard Moore
On 3 May 2014 22:42, Thiago Macieira wrote: > Em sáb 03 maio 2014, às 22:23:30, Richard Moore escreveu: > > Simplifying the Cipher API > > == > > > > Currently, the QSslCipher API is pretty large. It's not simply the > > code in the QSslCipher class itself, but also all th

Re: [Development] RFC: Managing the Addition of New SSL Backends

2014-05-04 Thread Konrad Rosenbaum
On Saturday 03 May 2014, Richard Moore wrote: > Support for QNAM > > > It's obvious that to be useful, a backend must allow QNAM to make SSL > requests. It need not support the more advanced features such as > client certs, custom CAs, custom cipher suites etc. > > In order to ha

Re: [Development] RFC: Managing the Addition of New SSL Backends

2014-05-03 Thread Thiago Macieira
Em sáb 03 maio 2014, às 22:23:30, Richard Moore escreveu: > - A small but significant number of apps use client certificates. > > - A small but significant number of apps use server SSL sockets. > > - Very few applications use custom trust stores. I'd say there's a specific case where all three

Re: [Development] RFC: Managing the Addition of New SSL Backends

2014-05-03 Thread Thiago Macieira
Em sáb 03 maio 2014, às 22:23:30, Richard Moore escreveu: > Simplifying the Cipher API > == > > Currently, the QSslCipher API is pretty large. It's not simply the > code in the QSslCipher class itself, but also all the stuff in the > QSslConfiguration that defines the prefe

[Development] RFC: Managing the Addition of New SSL Backends

2014-05-03 Thread Richard Moore
Introduction Qt provides a fairly powerful SSL API with support for a wide range of uses - SSL clients and servers can both be created. It provides extensive APIs for accessing information in SSL certificates, information about ciphers etc. In addition to the basics, it also includes