From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] libsec: add minimal support for the tls renegotiation extension
Date: Thu, 26 Jan 2023 16:52:25 -0500 [thread overview]
Message-ID: <d036de32-ed31-8ada-e41a-9a925a03e4ef@fjrhome.net> (raw)
In-Reply-To: <CAFSF3XMsKYgDx0tVhqB9i8C07aGNEiqWAGoScis9ffkoULR3Tg@mail.gmail.com>
Most common web browsers and many servers have dropped support for
anything older than 1.2, so pretending to be 1.1 is not likely to be
useful regardless.
On 1/26/23 3:54 PM, hiro wrote:
> i'm not sure what you're saying there. i think you don't understand
> the basics behind what a downgrade even is.
>
> me, i'm missing out on the details what the common clients out there
> demand to find as a minimum version.
>
> On 1/25/23, kemal <kemalinanc8@gmail.com> wrote:
>> 2023-01-25 17:30 GMT, kemal <kemalinanc8@gmail.com>:
>>> even if we tried to, the tls 1.3 spec mandates that the highest
>>> supported version must be stated as 1.2, and 1.3 support stated
>>> in a new extension. so i think we can't downgrade the handshake
>>> to 1.1 or 1.0.
>>>
>> actually, i'm wrong.
>> the client sends the first message. (clienthello)
>> so if we see that client supports at best 1.2, we could pretend
>> like we just support 1.1/1.0. but as i said before, the extension
>> can be used with 1.0 and 1.1, so this wouldn't help at all.
>>
next prev parent reply other threads:[~2023-01-26 21:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 2:24 Anthony Martin
2023-01-18 15:07 ` [9front] " Anthony Martin
2023-01-19 4:30 ` [9front] " ori
2023-01-19 4:48 ` ori
2022-11-10 2:24 ` Anthony Martin
2023-01-28 21:20 ` ori
2023-01-28 21:59 ` cinap_lenrek
2023-01-19 9:50 ` Anthony Martin
2023-01-20 12:12 ` hiro
2023-01-20 21:05 ` Anthony Martin
2023-01-20 22:33 ` hiro
2023-01-21 3:48 ` Anthony Martin
2023-01-21 12:54 ` hiro
2023-01-21 17:29 ` Steve Simon
2023-01-22 16:00 ` hiro
2023-01-22 7:55 ` Anthony Martin
2023-01-22 16:10 ` hiro
2023-01-23 11:18 ` Anthony Martin
2023-01-23 13:16 ` hiro
2023-01-23 14:24 ` Ori Bernstein
2023-01-23 14:29 ` Ori Bernstein
2023-01-24 0:14 ` hiro
2023-01-24 0:16 ` hiro
2023-01-25 16:19 ` kemal
2023-01-25 16:39 ` hiro
2023-01-25 17:07 ` kemal
2023-01-25 17:18 ` hiro
2023-01-25 17:30 ` kemal
2023-01-25 17:36 ` kemal
2023-01-26 20:54 ` hiro
2023-01-26 21:52 ` Frank D. Engel, Jr. [this message]
2023-01-27 6:11 ` kemal
2023-01-27 10:55 ` hiro
2023-01-27 17:38 ` kemal
2023-01-23 16:23 ` hiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d036de32-ed31-8ada-e41a-9a925a03e4ef@fjrhome.net \
--to=fde101@fjrhome.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).