IETF Logo Mail Archive

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

Rick van Rein <rick@openfortress.nl> Sat, 15 October 2022 19:18 UTC

Return-Path: <vanrein@vanrein.org>
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 0681EC14F719 for <kitten@ietfa.amsl.com>; Sat, 15 Oct 2022 12:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level:
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kpnmail.nl
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 5Dzs-bAlz0ma for <kitten@ietfa.amsl.com>; Sat, 15 Oct 2022 12:18:25 -0700 (PDT)
Received: from ewsoutbound.kpnmail.nl (ewsoutbound.kpnmail.nl [195.121.94.170]) (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 E9A24C14F606 for <kitten@ietf.org>; Sat, 15 Oct 2022 12:18:23 -0700 (PDT)
X-KPN-MessageId: 1d183344-4cbe-11ed-8a67-005056ab378f
Received: from smtp.kpnmail.nl (unknown [10.31.155.40]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id 1d183344-4cbe-11ed-8a67-005056ab378f; Sat, 15 Oct 2022 21:18:13 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kpnmail.nl; s=kpnmail01; h=content-type:mime-version:message-id:subject:to:from:date; bh=d2ckDRH9XQ/EYGAsLL5XBzaScRvrSDLXXoBRAP0ejBA=; b=s401QL1NEdcBvq4jEt18V0OSS/Hy5Mt2YePmkQ15uvYoj3DK8gBlQHFL58gE8cy3A12kNa7ox9/hp jYqNCZvnqbMxQ8dlVsI4R+S/v9fdi9gekXOss7Z0MK4M6lG912tVdIh+7e/UJZPADNFhebvvvGoID8 STd3HWZhNOI06l8Q=
X-KPN-MID: 33|cN0b6i7o/Ck6MZO4ivg07RipQyjLL8uGD/uz7/K4P1RZQMjiQY216UOQQuorJ+4 HXNc3FFyYf869AeE/jB781nWcABa06Tqch8SXHeoiO4g=
X-KPN-VerifiedSender: No
X-CMASSUN: 33|0Rd8T7rrlysx44pqcIfPYtm4GhmKff23lAmGzT8jZ6vlgQ+x3GLofnX0mRYsEGQ bYBcwnKuVefBOBcgV4UybHw==
X-Originating-IP: 77.173.183.203
Received: from fame.vanrein.org (77-173-183-203.fixed.kpn.net [77.173.183.203]) by smtp.xs4all.nl (Halon) with ESMTPSA id 219d129b-4cbe-11ed-9eb8-005056ab7584; Sat, 15 Oct 2022 21:18:21 +0200 (CEST)
Received: by fame.vanrein.org (Postfix, from userid 1000) id E1EF529D64; Sat, 15 Oct 2022 19:18:20 +0000 (UTC)
Date: Sat, 15 Oct 2022 19:18:20 +0000
From: Rick van Rein <rick@openfortress.nl>
To: Ken Hornstein <kenh@pobox.com>
Cc: Stefan Marsiske <03cx8i55f6@ctrlc.hu>, kitten@ietf.org
Message-ID: <20221015191820.GB11187@openfortress.nl>
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>
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/H3nH6e5JSZqwCO4uU1VtBIQ01aY>
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 19:18:36 -0000

Hello Ken,

> 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?

Then yes.  The reason we used Native Messaging is not directly needed
for HTTP-SASL, but we used it because

 1. this can access Kerberos5 credentials
 2. passwords for HTTP are best kept out of reach of JavaScript

-Rick

v2.23.0 | Report a Bug | By Email