On Fri, Dec 26, 2014 at 10:12 PM, Thiago Macieira
wrote:
> On Friday 26 December 2014 16:55:34 Mikkel Krautz wrote:
>> We definitely wouldn't keep supporting TLS 1.0 in that case.
>>
>> But we would like to still be able to accept connections where the
>> handshake ends up using TLS 1.0. Then we c
On Friday 26 December 2014 16:55:34 Mikkel Krautz wrote:
> We definitely wouldn't keep supporting TLS 1.0 in that case.
>
> But we would like to still be able to accept connections where the
> handshake ends up using TLS 1.0. Then we can handle the rejection at
> the application protocol level, an
On Fri, Dec 26, 2014 at 2:47 PM, Thiago Macieira
wrote:
>
> On Friday 26 December 2014 13:12:47 Mikkel Krautz wrote:
> > too!). So, the current QSsl::SecureProtocols in Qt 5.4 is fine for our use.
> > But since QSsl::SecureProtocols is a moving target, we're afraid that if we
> > commit to using i
On Friday 26 December 2014 13:12:47 Mikkel Krautz wrote:
> too!). So, the current QSsl::SecureProtocols in Qt 5.4 is fine for our use.
> But since QSsl::SecureProtocols is a moving target, we're afraid that if we
> commit to using it, a future Qt 5.x version may remove TLS 1.0 support. That
> would
Hi,
For Mumble (http://mumble.info), we'd like the ability to select the
allowed protocols for a QSslSocket in more fine-grained manner.
Very old versions of Mumble, version 1.x, used SSLv3, where as newer
versions,
1.2 and above, use TLSv1.0. We'd like to upgrade to TLSv1.2, and we also
need
bac
