IETF Logo Mail Archive

Re: [kitten] SASL as authmode for HTTP and SIP

Ken Hornstein <kenh@pobox.com> Sat, 15 October 2022 15:11 UTC

Return-Path: <kenh@pobox.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F24BC1524D5 for <kitten@ietfa.amsl.com>; Sat, 15 Oct 2022 08:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (1024-bit key) header.d=pobox.com
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 hO_0kQvAvILZ for <kitten@ietfa.amsl.com>; Sat, 15 Oct 2022 08:11:46 -0700 (PDT)
Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32F79C1524BB for <kitten@ietf.org>; Sat, 15 Oct 2022 08:11:45 -0700 (PDT)
Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 28A3B14CFA1; Sat, 15 Oct 2022 11:11:44 -0400 (EDT) (envelope-from kenh@pobox.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:in-reply-to:references:mime-version:content-type :content-transfer-encoding:date:message-id; s=sasl; bh=/2/ZPKX27 8cD4JlnXWXaKKHuxGvNaNi53byueBjt72M=; b=Ij3EBpkX2KgEngEyUJcOfZaCX TkJV5WRtSiJco5vUqkUA+rjYXVYtb2DnXr8G/bAKzrE+fJsFPJLRdsOj1w+P5n8q dc7bfZvOC6UR58kKl+9rRHfVNv2ebDSQxTl0UGmFEmXfnZtu113gxRKvsKWvFIRN YSPbncFZh6jrfvTUF0=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 1FCB114CFA0; Sat, 15 Oct 2022 11:11:44 -0400 (EDT) (envelope-from kenh@pobox.com)
Received: from pietro.internal (unknown [72.66.57.248]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 8289114CF9F; Sat, 15 Oct 2022 11:11:43 -0400 (EDT) (envelope-from kenh@pobox.com)
From: Ken Hornstein <kenh@pobox.com>
To: Stefan Marsiske <03cx8i55f6@ctrlc.hu>
cc: Rick van Rein <rick@openfortress.nl>, kitten@ietf.org
In-Reply-To: <Y0qP6nnIwmWxhz71@localhost>
References: <20221014171909.GB7961@openfortress.nl> <20221014231838.8881E16156F@pb-smtp2.pobox.com> <Y0nxyhwV75SoBuvB@localhost> <20221015004519.5B6F21C2CB0@pb-smtp21.pobox.com> <Y0qP6nnIwmWxhz71@localhost>
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4 WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 15 Oct 2022 11:11:42 -0400
X-Pobox-Relay-ID: ADADFE9C-4C9B-11ED-9F0B-2AEEC5D8090B-90216062!pb-smtp1.pobox.com
Message-Id: <20221015151144.1FCB114CFA0@pb-smtp1.pobox.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/hqiEBaITxF2no3LifKDHaTe3IVM>
Subject: Re: [kitten] SASL as authmode for HTTP and SIP
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Oct 2022 15:11:50 -0000

>tl;dr: the blocking webrequest API will be restricted in MV3 - which is
>necessary as far as i know from digging deep into this pit
>
>for more info, the 2nd half of my post goes more into detail:
>https://www.ctrlc.hu/~stef/blog/posts/On_OPAQUE,_SASL,_Google,_browser-extensions,_privacy_and_security.html

Okay, thank you!

I've been where you are now ... writing proxies and various plug-ins.  Have
you considered ever writing a patch to Chromium so that protocol actually ends
up in the base distribution?  I think that's the only long-term viable
solution at least on the browser side.

--Ken

v2.23.0 | Report a Bug | By Email