I do not support adoptions. I believe that arguments have already been
layed out in:
https://datatracker.ietf.org/doc/draft-jackson-tls-trust-is-nonnegotiable/
As an SSL implementer, I am highly unlikely to include this draft in my
library.
bob
__
On 6/7/24 2:36 PM, Eric Rescorla wrote:
On Fri, Jun 7, 2024 at 11:41 AM D. J. Bernstein wrote:
Eric Rescorla writes:
> I'm struggling to understand what people think is at stake here.
The WG will soon be faced with decisions regarding which curve+PQ
hybrids to recommend for T
On 4/12/23 6:03 PM, Martin Thomson wrote:
I think that is also true for NSS, though my experience of this is not
thorough. As David notes, client certificates are something of a mess once you
step outside a context where the client already knows what it should be sending.
On the server side,
On 3/27/23 8:28 AM, Yannick LaRue wrote:
Furthermore, our proposal to use ECDHE for securing connections
without a certificate provides the same level of assurance as the use
of low-assurance certificates, such as those issued by Let's Encrypt
or Cloudflare, which do not guarantee the identi
On 8/9/22 4:12 PM, Eric Rescorla wrote:
n Tue, Aug 9, 2022 at 4:08 PM Benjamin Kaduk wrote:
On Tue, Aug 09, 2022 at 03:59:01PM -0700, Eric Rescorla wrote:
>
3. Are you aware of some other set of rules for certificate issuance
that require
revocation after the certificate has expir
On 8/6/22 11:40 AM, Phillip Hallam-Baker wrote:
+1
Anything the WG does has to be proof against Quantum Cryptanalysis and
LoW (Laptops on Weekends). The fact that the broken algorithms did not
get picked does not change the fact that they made it to the third round.
Lumping all the algorithm
On 10/01/2019 04:39 AM, Hubert Kario wrote:
On Monday, 30 September 2019 15:56:19 CEST Jeremy Harris wrote:
On 30/09/2019 14:36, Christopher Wood wrote:
On Mon, Sep 30, 2019, at 6:28 AM, Hubert Kario wrote:
Clients must therefore
bound the number of parallel connections they init
On 10/22/2015 06:29 AM, Eric Rescorla wrote:
From an implementation perspective, I wouldn't be surprised if client
implementations choked on the server sending this. I had to check
to see if NSS would do so. It doesn't, but given the way the code
is written, it wouldn't have surprised me if it
On 08/28/2015 08:17 PM, Geoffrey Keating wrote:
Jeffrey Walton writes:
Also, if DSA was to be supported, one would need to specify how to
determine the hash function (use of fixed SHA-1 doesn't fly). And
1024-bit prime is too small.
FIPS186-4 (http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.
