[Secdispatch] Re: secure local IPC without HTTPS (was Re: Re: Y2K29 (was Re: DISPATCH/SECDISPATCH - Call for topics for Vienna))

Nico Williams <nico@cryptonector.com> Tue, 09 June 2026 17:44 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: secdispatch@mail2.ietf.org
Delivered-To: secdispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id BA60FFE32805; Tue, 9 Jun 2026 10:44:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781027084; bh=rTrOB0iqT7XOgdU80eaWE177xqrmNpucLU2/Z53NLlU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ACH6S5udD+hlfX8LFxkf/vkgCWe01lv8/p+Dn86IF8Od1zytge/ujXXdnCI3cIbtE x+RQPHhSOe5As8m4bNp8x4hZ62FseYw1CstsrhEvDo2swB3bLd1RAunJucZ6xBYjyr PrLfIX+91RWJLUDH5GUr0G4axRo8cKyoyKFegw+g=
X-Virus-Scanned: amavisd-new at ietf.org
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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cryptonector.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c3XERAf_7Lk1; Tue, 9 Jun 2026 10:44:44 -0700 (PDT)
Received: from zebra.cherry.relay.mailchannels.net (zebra.cherry.relay.mailchannels.net [23.83.223.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 227E0FE32800; Tue, 9 Jun 2026 10:44:44 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id F1BE3463CB7; Tue, 09 Jun 2026 17:44:36 +0000 (UTC)
Received: from pdx1-sub0-mail-a229.dreamhost.com (100-105-229-137.trex-nlb.outbound.svc.cluster.local [100.105.229.137]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 946FE463F3A; Tue, 09 Jun 2026 17:44:36 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Spicy-Language: 74faaffa0b223811_1781027076875_3487725853
X-MC-Loop-Signature: 1781027076875:2750852097
X-MC-Ingress-Time: 1781027076875
Received: from pdx1-sub0-mail-a229.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.105.229.137 (trex/7.1.5); Tue, 09 Jun 2026 17:44:36 +0000
Received: from ubby (unknown [24.28.102.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a229.dreamhost.com (Postfix) with ESMTPSA id 4gZbrg6cbBz3J; Tue, 9 Jun 2026 10:44:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1781027076; bh=uoOmrTBihlVh3/09LpfnllH+tTH2X3l4RhJL16yBssA=; h=Date:From:To:Cc:Subject:Content-Type; b=pXq2Kyv+MfrLMyyuM4nnWZO66fR8KQ8PK5kWygCg0I08dEylUb6Ju2as+R9iuHiyn B5elUjkLiRXq9wQRCFZwFO9ix+JteBX7GSgmuUuGh/KDCg7HKyx7D1gsL+t5TxI3K5 key2U851WsyBe74pvlFRGMbvS7Rtst40oePUqkmhC1gWhT4+7hS9uhFKcmlwyDi6nk /3wyrjD9Z5olKLv1MmSSt0SsxRGCWmidt+k4p2RdhUaHsQJ3rNX9V/LFFuixziOMF8 IOFuPhx9GgDNZSO3Ohn8ve9XzmtVk7GCIS8wWuUNViNLpno+SvJbLXkic75H1rmSM7 EjZrC3xEA6M2w==
Date: Tue, 09 Jun 2026 12:44:33 -0500
From: Nico Williams <nico@cryptonector.com>
To: Demi Marie Obenour <demiobenour@gmail.com>
Message-ID: <aihRAam1umg5lujx@ubby>
References: <CADNypP_zNn_AQKCxodeStDPnJvVqNyXqzEZhUXGr8Otgr7xMYA@mail.gmail.com> <aiOZvQO9xA958azm@ubby> <aiT1rDQF9rT3oajf@ubby> <5AC11ABD-CF83-4F68-A53E-4304E4DF803A@proper.com> <CABcZeBPccub39EJqpBh7BGrVcg5X5sN5n3d=AsPEozKkVM_Ztw@mail.gmail.com> <CAF8qwaB7WpO49_dc9KX2TbQ__gzucXX1OdvpHYpdeFp+6yOi=Q@mail.gmail.com> <aicx928q9ynDcMeK@ubby> <28401.1781019987@obiwan.sandelman.ca> <aig6YeCNBK2lD1r2@ubby> <baa0aa8a-22c1-47d6-a7b5-20164460b9a5@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <baa0aa8a-22c1-47d6-a7b5-20164460b9a5@gmail.com>
Message-ID-Hash: XTMITQYPDDKYLU6ETI2TO44RLKSNP7WR
X-Message-ID-Hash: XTMITQYPDDKYLU6ETI2TO44RLKSNP7WR
X-MailFrom: nico@cryptonector.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-secdispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Michael Richardson <mcr+ietf@sandelman.ca>, dispatch@ietf.org, secdispatch <secdispatch@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Secdispatch] Re: secure local IPC without HTTPS (was Re: Re: Y2K29 (was Re: DISPATCH/SECDISPATCH - Call for topics for Vienna))
List-Id: Security Dispatch <secdispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/mpaLv8pKVpH-bfdUhNRAi8vtgGs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Owner: <mailto:secdispatch-owner@ietf.org>
List-Post: <mailto:secdispatch@ietf.org>
List-Subscribe: <mailto:secdispatch-join@ietf.org>
List-Unsubscribe: <mailto:secdispatch-leave@ietf.org>

On Tue, Jun 09, 2026 at 01:43:08PM -0400, Demi Marie Obenour wrote:
> On 6/9/26 12:08, Nico Williams wrote:
> > But really, the actual IPC mechanisms are uninteresting.  What's
> > interesting is that a) they exist, b) the protocol spoken over those,
> > and for (b) I'm proposing HTTP (http:, not https:, since it's local
> > IPC).  Why HTTP?  Because caching is integral to it, and because the
> > protocols in question will be very similar to token issuer protocols we
> > already have, so commonality for IAM implementations is a given, and
> > that means less effort to implement.
> 
> Ah, I see that this is for token issuing, not cert validation.

No, it's both.  (Though the various services provided can be provided by
different IPC end-points.)

Nico
--