IETF Logo Mail Archive

Re: [art] Auto-configuring Email Clients via WebFinger

"John Levine" <johnl@taugh.com> Tue, 16 July 2019 22:05 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA52120132 for <art@ietfa.amsl.com>; Tue, 16 Jul 2019 15:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=I4nyoM0L; dkim=pass (1536-bit key) header.d=taugh.com header.b=UzBgVmgb
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KRKKJK4t6XVP for <art@ietfa.amsl.com>; Tue, 16 Jul 2019 15:05:21 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80A0112012C for <art@ietf.org>; Tue, 16 Jul 2019 15:05:21 -0700 (PDT)
Received: (qmail 16423 invoked from network); 16 Jul 2019 22:05:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=4025.5d2e4a20.k1907; i=johnl-iecc.com@submit.iecc.com; bh=D7r+Dawexz8nDj7RIYaBkb6alroHR/6UCxcitjTj5FE=; b=I4nyoM0LrmQFrv1ImxEE/5ToN8HcbzUPLqSPlzWPT9UoLq0LE3KYYWOggh593AWwwH9X4lO4cNZsiLMZRSSxl5YyfROu9XK6irLfU+VUZhtotXyucF7OY7O1AfdHv8nBKfRKT8jk41yRzrt7XgbyAmDQfSEdrK2D15mQOe7tPOgEYHuNs+xkEkYvKHtQAzNdIkTXh0gHzyGdZklzA8PUbnEZUgV53mYiOLta7lfOQzLjPdZUi97sUZRrV09+5VYw
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=4025.5d2e4a20.k1907; olt=johnl-iecc.com@submit.iecc.com; bh=D7r+Dawexz8nDj7RIYaBkb6alroHR/6UCxcitjTj5FE=; b=UzBgVmgbNbTNwC1U7p5rzehPYUGJTds9ru19RVzjU6J035HLC2AcISmq4zzHQoDPuEcasRiTYe7QWntfBO2FAOgnmbyoReZGSM0/A4BssXCsXH2HEbsr7q8IMfGxkdsQ0W738aLHlWnp7hsrtlFUNRI4Fuztq3zoGUCLbJBjVBp1bfmt/lNYIgquc1B/lRj1fWxaSu9I1eCD3HoSVWhy+zf+duvIXnpySxD/VDu3jgcLGiAcxrqdYXqZmCaYozyA
Received: from ary.qy ([64.246.232.221]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP; 16 Jul 2019 22:05:20 -0000
Received: by ary.qy (Postfix, from userid 501) id A420450758F; Tue, 16 Jul 2019 18:05:19 -0400 (EDT)
Date: Tue, 16 Jul 2019 18:05:19 -0400
Message-Id: <20190716220519.A420450758F@ary.qy>
From: John Levine <johnl@taugh.com>
To: art@ietf.org
Cc: masinter@gmail.com
In-Reply-To: <7D0473AF-20BA-42AC-806B-EC1DE7610BEF@gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ERd2WIcfrGhjx4XUXKivZAvkLOw>
Subject: Re: [art] Auto-configuring Email Clients via WebFinger
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2019 22:05:23 -0000

In article <7D0473AF-20BA-42AC-806B-EC1DE7610BEF@gmail.com> you write:
>-=-=-=-=-=-
>
>> Putting passwords in cleartext in the request uri is ill advised because many servers keep logs of requests, caches, etc

Good point.

Plan A: if the server needs the user name and password, it sends back
a 401 response and the MUA sends them via RFC 7617 basic
authentication.  That seems largely backward compatible and invents a
minimum of new stuff.

Plan B: do it as a POST like most web password entries.  I realize
this has backward compatibility issues with the current GET.

v2.23.0 | Report a Bug | By Email