[TLS] Trusting self-signed TLS certificates - specifically for HTTPS
Ollie <me@olliejc.uk> Sun, 20 November 2022 13:11 UTC
Return-Path: <me@olliejc.uk>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46DDDC14F72F for <tls@ietfa.amsl.com>; Sun, 20 Nov 2022 05:11:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=olliejc.uk
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rh_zL3z8ZucD for <tls@ietfa.amsl.com>; Sun, 20 Nov 2022 05:11:23 -0800 (PST)
Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B803C14F6EB for <tls@ietf.org>; Sun, 20 Nov 2022 05:11:22 -0800 (PST)
Date: Sun, 20 Nov 2022 13:11:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=olliejc.uk; s=protonmail3; t=1668949879; x=1669209079; bh=5YkDVdMtS0dJfaw56QyY20cxCp8ueFllW/M5KQnpTPo=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=vND0wqXRlD0vvmOJHKkYVBLd0hyowAzzr55NH5MR+pOE0rTe/I30D3QN3e4HZ9tUB xR6q98CVYkroRmwg8QqtIpLokOQQd0IbvWudCPoRhiq4gjuVj3LMMqCXiGL03Uo+vP egbN5c7pW+CKJXrVt79JI0UlI32BdjyABOOCS44kcms+SWCJWz6pwQ4l9cvwstRXsp 6lW4vpzFhp3piwonoDB+pgnupRm0KmH/Ae5FpuS/Gy69/mZK/gASsClyJBTe1EBHs2 6wEdwZsJKWvUgbJ+bLt+7b0nMY0ON6x2FIeMNkuzO2VAO0sp/UmzdABuzTMc6QGB3Z hLP2flgHvzshA==
To: tls <tls@ietf.org>
From: Ollie <me@olliejc.uk>
Message-ID: <9jom-o0k2EKlsgFmAQfJqg2oBOK_bEw9D1VvMz3nmF4L4K1vftMPU916SKERU48MSk10IakHBzdPD74CMFYha65rdhg-8PqDpPpArSfYuPI=@olliejc.uk>
Feedback-ID: 19765882:user:proton
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_GjuGxJZ3hrl2xUUwY3F11lqsJt3ceAfqxp9BYy04M"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/ndAo75C3RQ3kdAsPT5QCrsVs-EE>
X-Mailman-Approved-At: Mon, 28 Nov 2022 11:21:18 -0800
Subject: [TLS] Trusting self-signed TLS certificates - specifically for HTTPS
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Nov 2022 13:12:41 -0000
Hi folks, I'm new to the I-D/RFC process so apologies for any naivety! Firstly, I've done a quick search for any commentary around this but haven't found anything specific - but let me know if I've likely missed something. I want to propose a way for a user agent to trust self-signed certificates. Is this best discussed here in TLS, or perhaps over at HTTP? In essence, I'm proposing that user agents should trust a fully DNSSEC domain with a TLS certificate set up using DANE, along with changes to CT log submission process to allow self-signed certificates (looking to suggest via rfc9162). I've set up an example site and GitHub repo with more details: - https://justselfsigned.org - https://github.com/OllieJC/justselfsigned.org It'd be great to get your thoughts and support to progress this. Thanks, Ollie
- [TLS] Trusting self-signed TLS certificates - spe… Ollie
- Re: [TLS] Trusting self-signed TLS certificates -… Eric Rescorla
- Re: [TLS] Trusting self-signed TLS certificates -… Viktor Dukhovni
- Re: [TLS] Trusting self-signed TLS certificates -… Bas Westerbaan
- Re: [TLS] Trusting self-signed TLS certificates -… Viktor Dukhovni
- Re: [TLS] Trusting self-signed TLS certificates -… Eric Rescorla
- Re: [TLS] Trusting self-signed TLS certificates -… Viktor Dukhovni
- Re: [TLS] Trusting self-signed TLS certificates -… Bas Westerbaan
- Re: [TLS] Trusting self-signed TLS certificates -… Ollie
- Re: [TLS] Trusting self-signed TLS certificates -… Viktor Dukhovni
- Re: [TLS] Trusting self-signed TLS certificates -… Bas Westerbaan
- Re: [TLS] Trusting self-signed TLS certificates -… Ollie
- Re: [TLS] Trusting self-signed TLS certificates -… Viktor Dukhovni
- Re: [TLS] Trusting self-signed TLS certificates -… Bas Westerbaan
- Re: [TLS] Trusting self-signed TLS certificates -… Ollie
- Re: [TLS] Trusting self-signed TLS certificates -… Viktor Dukhovni
- Re: [TLS] Trusting self-signed TLS certificates -… Ollie
- Re: [TLS] Trusting self-signed TLS certificates -… Viktor Dukhovni