I suppose Facebook reports 50% because their mobile apps uses their SSL
library Fizz with Tls 1.3
https://thehackernews.com/2018/08/fizz-tls-ssl-library.html
I'm curious seeing your telemetry info now. Chrome 70 was released last
week, and FireFox 63 today, with TLS 1.3 support
regards
Le mer.
>The users who delay or block automatic updates tend to greatly overlap
with the users who actively block remote telemetry of their update
habits, thus skewing such statistics of "get almost full coverage within
a month or two".
But not downloads. :)
Shrug.
--
openssl-users
On 18/09/2018 19:11, Salz, Rich via openssl-users wrote:
My point was about the likelihood of last-draft browsers lingering
on in the real world for some time (like 1 to 3 years) after the
TLS1.3-final browser versions ship.
I do not think this is a concern. Chrome and FF
On Tue, Sep 18, 2018 at 05:11:42PM +, Salz, Rich via openssl-users wrote:
> >My point was about the likelihood of last-draft browsers lingering
> on in the real world for some time (like 1 to 3 years) after the
> TLS1.3-final browser versions ship.
>
> I do not think this is a
>My point was about the likelihood of last-draft browsers lingering
on in the real world for some time (like 1 to 3 years) after the
TLS1.3-final browser versions ship.
I do not think this is a concern. Chrome and FF auto-update and get almost
full coverage within a month or two,
On 15/09/2018 10:46, Kurt Roeckx wrote:
On Thu, Sep 13, 2018 at 08:13:41PM +0200, Jakob Bohm wrote:
On 13/09/2018 09:57, Klaus Keppler wrote:
Hi,
thank you for all your responses.
I've just tested with Firefox Nightly 64.0a1, and both s_server and our
own app (using OpenSSL 1.1.1-release)
On Thu, Sep 13, 2018 at 08:13:41PM +0200, Jakob Bohm wrote:
> On 13/09/2018 09:57, Klaus Keppler wrote:
> > Hi,
> >
> > thank you for all your responses.
> >
> > I've just tested with Firefox Nightly 64.0a1, and both s_server and our
> > own app (using OpenSSL 1.1.1-release) are working fine.
>
On 13/09/2018 21:47, Salz, Rich via openssl-users wrote:
Much work for little gain and purpose.
You can mix drafts, but mixing the draft and the official version is hard,
there's too many semantic changes (e.g., around fallback vs
no-fallback-protection).
Ok, from what others had said, the
Much work for little gain and purpose.
You can mix drafts, but mixing the draft and the official version is hard,
there's too many semantic changes (e.g., around fallback vs
no-fallback-protection).
--
openssl-users mailing list
To unsubscribe:
On Thu, Sep 13, 2018 at 08:13:41PM +0200, Jakob Bohm wrote:
> On 13/09/2018 09:57, Klaus Keppler wrote:
> >Hi,
> >
> >thank you for all your responses.
> >
> >I've just tested with Firefox Nightly 64.0a1, and both s_server and our
> >own app (using OpenSSL 1.1.1-release) are working fine.
> >
>
On 09/13/2018 02:13 PM, Jakob Bohm wrote:
On 13/09/2018 09:57, Klaus Keppler wrote:
Hi,
thank you for all your responses.
I've just tested with Firefox Nightly 64.0a1, and both s_server and our
own app (using OpenSSL 1.1.1-release) are working fine.
The Firefox website is quite confusing:
On 13/09/2018 09:57, Klaus Keppler wrote:
Hi,
thank you for all your responses.
I've just tested with Firefox Nightly 64.0a1, and both s_server and our
own app (using OpenSSL 1.1.1-release) are working fine.
The Firefox website is quite confusing:
Firefox 61 is already shipping draft-28,
Hi,
thank you for all your responses.
I've just tested with Firefox Nightly 64.0a1, and both s_server and our
own app (using OpenSSL 1.1.1-release) are working fine.
The Firefox website is quite confusing:
> Firefox 61 is already shipping draft-28, which is essentially the same as the
> final
On 09/12/2018 04:46 PM, Juan Isoza wrote:
As I understand and check:
https://www.tls13.net accept connexion from final openssl-1.1.1
(RFC8446) but not from openssl-1.1.1 pre8 (draft 28)
At this point the protocol is published and the OpenSSL 1.1.1 release is
done. You should not be
As I understand and check:
https://www.tls13.net accept connexion from final openssl-1.1.1 (RFC8446)
but not from openssl-1.1.1 pre8 (draft 28)
https://tls13.crypto.mozilla.org accept connexion from openssl-1.1.1 pre8
(draft 28) but not from final openssl-1.1.1 (RFC8446)
On 09/12/2018 12:06 PM, Angus Robertson - Magenta Systems Ltd wrote:
IIUC, only Firefox nightly as of approximately today will support
the final RFC 8446 version;
Firefox 63.0b5 works OK with OpenSSL 1.1.1, think it came Tuesday.
Even Firefox/60.0 works.
> Some Chrome browsers seem to be hitting https://www.tls13.net/
> with versions from Chrome/70.0.3534.4 upwards to Chrome/71.0.3544.0
Some of my public web servers are now on yesterday's version, three
TLSv1.3 users today, two with Firefox 63, one with
Chrome/68.0.3440.106+Safari/537.36.
I
> IIUC, only Firefox nightly as of approximately today will support
> the final RFC 8446 version;
Firefox 63.0b5 works OK with OpenSSL 1.1.1, think it came Tuesday.
https://download.mozilla.org/?product=firefox-beta-stub=win=en-U
S
> I haven't looked into Chrome yet.
My versions don't work
On 09/12/2018 09:50 AM, Klaus Keppler wrote:
Hi,
when I create a TLS-1.3-only "web" server with s_server (from OpenSSL
1.1.1-release), Firefox/Chrome can't access it.
Be sure to use Firefox nightly version 64.0a1 and upwards. Anything less
and you may be getting draft 28 support and NOT
On 09/12/2018 10:44 AM, Viktor Dukhovni wrote:
On Sep 12, 2018, at 10:41 AM, Viktor Dukhovni
wrote:
IIUC, only Firefox nightly as of approximately today will support the final
RFC 8446 version; I haven't looked into Chrome yet.
From the Firefox TLS 1.3 blog entry:
> On Sep 12, 2018, at 10:41 AM, Viktor Dukhovni
> wrote:
>
>> IIUC, only Firefox nightly as of approximately today will support the final
>> RFC 8446 version; I haven't looked into Chrome yet.
>
> From the Firefox TLS 1.3 blog entry:
>
>
> On Sep 12, 2018, at 10:20 AM, Benjamin Kaduk via openssl-users
> wrote:
>
> IIUC, only Firefox nightly as of approximately today will support the final
> RFC 8446 version; I haven't looked into Chrome yet.
From the Firefox TLS 1.3 blog entry:
On Wed, Sep 12, 2018 at 03:50:17PM +0200, Klaus Keppler wrote:
> Hi,
>
> when I create a TLS-1.3-only "web" server with s_server (from OpenSSL
> 1.1.1-release), Firefox/Chrome can't access it.
> According to all docs I've read so far, the TLS 1.3 implementations both
> from Firefox (62.x) and
23 matches
Mail list logo