IETF Logo Mail Archive

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

Stefan Marsiske <03cx8i55f6@ctrlc.hu> Sat, 15 October 2022 10:48 UTC

Return-Path: <03cx8i55f6@ctrlc.hu>
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 CD3ACC14CF0F for <kitten@ietfa.amsl.com>; Sat, 15 Oct 2022 03:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.885
X-Spam-Level:
X-Spam-Status: No, score=-1.885 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 N_TgxC8T1bCv for <kitten@ietfa.amsl.com>; Sat, 15 Oct 2022 03:48:21 -0700 (PDT)
Received: from ctrlc.hu (ctrlc.hu [185.193.126.105]) by ietfa.amsl.com (Postfix) with ESMTP id 354FAC1522AD for <kitten@ietf.org>; Sat, 15 Oct 2022 03:48:13 -0700 (PDT)
Received: from i.ctrlc.hu (unknown [10.23.5.25]) by ctrlc.hu (Postfix) with ESMTP id 40B2C3E5ECE; Sat, 15 Oct 2022 10:48:11 +0000 (UTC)
Received: by i.ctrlc.hu (Postfix, from userid 1000) id F011DAA; Sat, 15 Oct 2022 10:48:10 +0000 (UTC)
Date: Sat, 15 Oct 2022 12:48:10 +0200
From: Stefan Marsiske <03cx8i55f6@ctrlc.hu>
To: Ken Hornstein <kenh@pobox.com>
Cc: Rick van Rein <rick@openfortress.nl>, kitten@ietf.org
Message-ID: <Y0qP6nnIwmWxhz71@localhost>
References: <20221014171909.GB7961@openfortress.nl> <20221014231838.8881E16156F@pb-smtp2.pobox.com> <Y0nxyhwV75SoBuvB@localhost> <20221015004519.5B6F21C2CB0@pb-smtp21.pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20221015004519.5B6F21C2CB0@pb-smtp21.pobox.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/yFU993tRRsX-ByUd6RTThTDFC5g>
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 10:48:25 -0000

On Fri, Oct 14, 2022 at 08:45:14PM -0400, Ken Hornstein wrote:
> >On Fri, Oct 14, 2022 at 07:18:37PM -0400, Ken Hornstein wrote:
> >> >The HTTP-SASL spec is mature, and has been implemented for Apache (2x),
> >> >Nginx and FireFox.
> >
> >the missing links:
> >https://gitlab.com/arpa2/apachemod/-/tree/master/
> >https://github.com/stef/ngx_http_auth_sasl_module/
> >https://gitlab.com/arpa2/http_sasl_client
> 
> Thank you!  That fills in the missing pieces.
> 
> It seems like Manifest V3 supports Native Messaging via
> chrome.runtime.connectNative() so in theory (if time was infinite)
> you could do something similar for Chrome, right?  Or am I once again
> missing something?

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

v2.23.0 | Report a Bug | By Email