IETF Logo Mail Archive

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

Austin Wright <aaa@bzfx.net> Wed, 17 July 2019 03:00 UTC

Return-Path: <aaa@bzfx.net>
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 7E35212013E for <art@ietfa.amsl.com>; Tue, 16 Jul 2019 20:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bzfx.net
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 74FLX5D3jWgi for <art@ietfa.amsl.com>; Tue, 16 Jul 2019 20:00:29 -0700 (PDT)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6DA9120131 for <art@ietf.org>; Tue, 16 Jul 2019 20:00:29 -0700 (PDT)
Received: by mail-pf1-x429.google.com with SMTP id p184so10069218pfp.7 for <art@ietf.org>; Tue, 16 Jul 2019 20:00:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bzfx.net; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gs4pflLi3bmJzEUrtfqCE+X48vO8YihWO01KnxO71v8=; b=a+iQ4RKlfvHaHiaJHsGirt20tGql0ie+kE7hFDcRChJMWMAY2OQrhYANfBs49KSa5d NIBBSJwbuoDNj6rtF2XTwPHWHusBoLzS7T3FxQ1LDoiqRCtkQvP9PbtsE5IQWcQ/wZvH kOmb8vbD3vaOfKjK8jGXPUOAFjDBqgZN4wkk0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gs4pflLi3bmJzEUrtfqCE+X48vO8YihWO01KnxO71v8=; b=rmddYm7mThdVypux/sNhYzje2YFnQVWIUH4h0FLOFDXTmOhufhJhwJzH6j8ZeiUo2Y JH19K+dqBFANeyWBnZHZpL/Cx/a2GedY2QHbC/aQm/PwcbT1xV5joRTM7zDbkeyLC3p5 i1Va3TGbcLgtfTnj7ru4oKAoFo+s5uFK5rlpic94fcTW/yXK2AkRoHfmwkyS97CNMGes PzPKA/8w94LZgvQhcqXhBWNYrd496sjwdeFf7iWSv0UsbfdFS++YTAqGLnF8T+5YiQVq TriaG2yhblSjyo0mLPz4y+ZdMbMUoxX+ZouWI/GWMVSWfnUlBCZa3IGB6GhG2L5aXGrC yDNg==
X-Gm-Message-State: APjAAAVUAnVEBX1hl33FBLfAMjfnx63L0RGI0TOAKZg0LNNFOjZI/1SD 07B8Wnq3TDIeRZ09Bwo2xyY=
X-Google-Smtp-Source: APXvYqwAWC34CZmJSxsAUJD2Zxv3FIoQpgKomHje65WqQlp09AAxwyfDz92qnW3ZYBVjdUZ74TXdzw==
X-Received: by 2002:a63:7d49:: with SMTP id m9mr26969265pgn.161.1563332428764; Tue, 16 Jul 2019 20:00:28 -0700 (PDT)
Received: from [192.168.0.13] (184-98-251-21.phnx.qwest.net. [184.98.251.21]) by smtp.gmail.com with ESMTPSA id 196sm24471191pfy.167.2019.07.16.20.00.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jul 2019 20:00:27 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Austin Wright <aaa@bzfx.net>
In-Reply-To: <20190716220519.A420450758F@ary.qy>
Date: Tue, 16 Jul 2019 20:00:25 -0700
Cc: art@ietf.org, masinter@gmail.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <3A04338D-CE01-4693-92AF-4AE5CB70A68F@bzfx.net>
References: <20190716220519.A420450758F@ary.qy>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/AjMmbeIAiqWxwqBZk3jPyOTeAf0>
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: Wed, 17 Jul 2019 03:00:32 -0000


> On Jul 16, 2019, at 15:05, John Levine <johnl@taugh.com> wrote:
> 
> 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.
> 

What are the risks if the mail server and HTTP server are maintained by different authorities?

Cheers,

Austin Wright.

v2.23.0 | Report a Bug | By Email