Re: [whatwg/fetch] Clarification on CORS preflight fetches for TLS client certificates (#869) from eyeinsky on 2021-03-17 (public-webapps-github@w3.org from March 2021)

From: eyeinsky <notifications@github.com>
Date: Wed, 17 Mar 2021 09:55:03 -0700
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/869/801245754@github.com>

@sleevi Hi, I had another review of this thread and I still believe sending client certificates during a preflight imposes no security issue. To rehash:
- `OPTIONS` request is as safe as a `GET`, and `GET` with credentials is allowed by the spec
- client certificate authentication doesn't appear to be a hack (where is this info coming from?) as it's the same X.509 certificate verification any browser does for a HTTPS website, but what now the server does for the client.

The Secondary Certificates and CATCH drafts seem unrelated as they are are either a solution to trigger TLS renegotiation with a HTTP header or request a certificate in an ongoing TLS session to avoid a full renegotiation. Prompting for a certificate in a preflight wants a mutually authenticated session from the start.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/869#issuecomment-801245754

Received on Wednesday, 17 March 2021 16:55:19 UTC