Re: [apps-discuss] Webfinger discussion

"Paul E. Jones" <paulej@packetizer.com> Tue, 27 March 2012 16:57 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDADC21E8222 for <apps-discuss@ietfa.amsl.com>; Tue, 27 Mar 2012 09:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level:
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bGCBm7kCSHGJ for <apps-discuss@ietfa.amsl.com>; Tue, 27 Mar 2012 09:57:31 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 1E1F221E80D0 for <apps-discuss@ietf.org>; Tue, 27 Mar 2012 09:57:31 -0700 (PDT)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id q2RGvSn8012362 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 27 Mar 2012 12:57:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1332867449; bh=7q2ca26y+fe6cNccSJtBAOFJUPA5BPKBE2/YyidVq9E=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=pTiLp4XoN9pPPFPPGBAt6VDa17hIes7A11aIWovWmLcGiVZI0JtVHiOeecMGGbCbr rfKKkVI+eJKhTTeJMO3jK2dKabkAM7sBdcsUSL/oh4kH0QLH6qBw01E0+IIC4geth0 UX62tDqUgiW+9dGF23jKGua4ODy+BbsgKYekICek=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'James M Snell' <jasnell@gmail.com>
References: <053201cd0b5d$c08c80f0$41a582d0$@packetizer.com> <20120326150556.GC3557@mail.yitter.info> <CAA1s49V0M7N1pLua+ORxGWmsrd_yAA_KQ0Piqjg8VuWJ5=G+Lg@mail.gmail.com> <20120327084709.GB11491@mail.yitter.info> <00ac01cd0c34$cfc96f10$6f5c4d30$@packetizer.com> <CABP7RbdtMYtqgV=NepJMNintjF9hb4h6wv2ttc5bDVqE=yAvPA@mail.gmail.com>
In-Reply-To: <CABP7RbdtMYtqgV=NepJMNintjF9hb4h6wv2ttc5bDVqE=yAvPA@mail.gmail.com>
Date: Tue, 27 Mar 2012 12:57:31 -0400
Message-ID: <00d201cd0c3a$b3672410$1a356c30$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEg174HJISLlkWDD0VVkXSpmVuZQwKMareXAWwgTx8BwaaRJQGG5wouAU3B5AaXkk7QgA==
Content-Language: en-us
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Webfinger discussion
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2012 16:57:32 -0000

James,

If the other items are editorial, perhaps just direct them to me.  If they are items that others might want to weigh in on, then this list is the appropriate venue.

Paul

> -----Original Message-----
> From: James M Snell [mailto:jasnell@gmail.com]
> Sent: Tuesday, March 27, 2012 12:39 PM
> To: Paul E. Jones
> Cc: Andrew Sullivan; apps-discuss@ietf.org
> Subject: Re: [apps-discuss] Webfinger discussion
> 
> To be fair, there are ways of dealing with the potential for security
> leaks of this nature with WebFinger that did not really exist with the
> original Finger protocol. OAuth 2, for instance. A WebFinger endpoint
> could choose to serve up only the most basic static information to
> unauthenticated requesters, but then provide a means for a requester to
> authenticate and request permission from the target user or provider to
> acquire additional information as part of the response.
> 
> On a side note to Paul: I did have some additional general comments on the
> WebFinger spec itself, I wanted to ask where such comments would be best
> directed for discussion.
> 
> - James
> 
> On Tue, Mar 27, 2012 at 9:15 AM, Paul E. Jones <paulej@packetizer.com>
> wrote:
> > I agree it would be useful to add text about sharing information that
> > might be dynamic in nature (e.g., current user location).
> >
> > We'll add text along those lines to the next draft.  Any other
> > security considerations we should note?
> >
> > Paul
> >
> >> -----Original Message-----
> >> From: apps-discuss-bounces@ietf.org
> >> [mailto:apps-discuss-bounces@ietf.org]
> >> On Behalf Of Andrew Sullivan
> >> Sent: Tuesday, March 27, 2012 4:47 AM
> >> To: apps-discuss@ietf.org
> >> Subject: Re: [apps-discuss] Webfinger discussion
> >>
> >> On Mon, Mar 26, 2012 at 02:31:30PM -0400, Bob Wyman wrote:
> >>
> >> > un-recommended!). If people did, in fact, use WebFinger to record
> >> > such stuff, the concerns you mentioned would be relevant. Thus, it
> >> > might make sense for the Security Considerations section to suggest
> >> > that one should think carefully before using WebFinger to provide
> >> > such dynamic
> >> information.
> >>
> >> Right, that's most of what I was trying to say.  I do have a concern
> >> that collecting a bunch of different information about a given person
> >> and linking it together in a single, easy to access repository has
> >> some potential security side effects (not just privacy ones, but
> >> those too, of
> >> course) that are not clearly highlighted in the security
> considerations.
> >> I suppose one could argue that facebook's (or pick your poison) user
> >> population shows nobody cares about that, but I think it would still
> >> be good to have some observations about those effects.
> >>
> >> Best,
> >>
> >> A
> >>
> >> --
> >> Andrew Sullivan
> >> ajs@anvilwalrusden.com
> >> _______________________________________________
> >> apps-discuss mailing list
> >> apps-discuss@ietf.org
> >> https://www.ietf.org/mailman/listinfo/apps-discuss
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss