IETF Logo Mail Archive

Re: [websec] Service auto-configuration and certificate pinning

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 23 June 2016 09:20 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88DEA12E12F for <websec@ietfa.amsl.com>; Thu, 23 Jun 2016 02:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level:
X-Spam-Status: No, score=-5.727 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_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 1wCl80i3cURp for <websec@ietfa.amsl.com>; Thu, 23 Jun 2016 02:19:56 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD5C012E138 for <websec@ietf.org>; Thu, 23 Jun 2016 02:14:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 3DBC1BE3E; Thu, 23 Jun 2016 10:14:33 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j8ykTf0GpIgc; Thu, 23 Jun 2016 10:14:26 +0100 (IST)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C534FBE80; Thu, 23 Jun 2016 10:14:02 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1466673243; bh=Xb2S64S+8ujYUy5cBjRzHF8HnGhU3Ik3/KQ64PLFkN4=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=DoPFqv7hDtMjnrsCLYS2M96j74KKW7uaiCavB1wxGSNFr+5+3wRSDdDR043HIaIoE CDotI+UitteSv+WSe7ceG09bnLlllNXAdENdm+xeNma9Hwum4hVGhzVgJIya/w3d3d kEhMv/9ectXH5WPebGGeSkmLGz+/KNUNyapdOKF0=
To: D.Rogers@gmx.net, Marten Gajda <marten@dmfs.org>
References: <576B0541.7040708@dmfs.org> <trinity-75a661ca-5da5-4e1f-a92c-5b52f3402490-1466672071054@3capp-gmx-bs77>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <576BA85A.6000507@cs.tcd.ie>
Date: Thu, 23 Jun 2016 10:14:02 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <trinity-75a661ca-5da5-4e1f-a92c-5b52f3402490-1466672071054@3capp-gmx-bs77>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms070109040907070609060309"
Archived-At: <https://mailarchive.ietf.org/arch/msg/websec/pmxjkGXMtEHR_Ma_lSiKtaxq4_M>
Cc: "websec@ietf.org" <websec@ietf.org>
Subject: Re: [websec] Service auto-configuration and certificate pinning
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/websec/>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2016 09:20:00 -0000


On 23/06/16 09:54, D.Rogers@gmx.net wrote:
> Hello Marten,
> it might be of interest to check out the 'Unbearable' group. they are working on 
> pinning bearer certficates.

For info: unbearable@ietf.org is the WG mailing list. The working
group is more prosaically named tokbind. [1] :-)

S.

[1] https://tools.ietf.org/wg/tokbind

> Regards
> Dean Rogers
> *Gesendet:* Mittwoch, 22. Juni 2016 um 23:38 Uhr
> *Von:* "Marten Gajda" <marten@dmfs.org>
> *An:* "websec@ietf.org" <websec@ietf.org>
> *Betreff:* [websec] Service auto-configuration and certificate pinning
> Hi list,
> 
> I'm currently working on an update of a draft that specifies a way for
> clients to configure themselves with a minimum of user-provided
> information. The current draft is available at
> https://tools.ietf.org/html/draft-daboo-aggregated-service-discovery-03
> (it's a bit outdated, but we're working on it).
> This draft specifies a member to contain a server certificate, which
> presumably was meant to support some sort of certificate pinning.
> 
> During my research on how to improve this I came across RFC 7469 and
> https://tools.ietf.org/html/draft-hallambaker-webseccaa-00
> 
> I'd like to ask the members of this list whether they think that
> "bootstrapping" certificate pinning for individual services (like so:
> https://github.com/CalConnect/AUTODISCOVERY/issues/8#issuecomment-227857982)
> would be useful to have in a service configuration document or if they
> have any concerns or other comments about this.
> 
> I'd also like to hear about opinions if this could be an acceptable
> solution for certificate pinning with non-HTTP based protocols, i.e. for
> protocols that don't have an in-band pinning mechanism the client would
> reload the service configuration document whenever the cached pinning
> information is outdated (i.e. <max-age> seconds have passed since it was
> downloaded).
> 
> Any comments (whether in response to this post or at GitHub) are very
> welcome.
> 
> Regards,
> 
> Marten Gajda
> 
> --
> Marten Gajda
> CEO
> 
> dmfs GmbH
> Schandauer Straße 34
> 01309 Dresden
> GERMANY
> 
> phone: +49 177 4427167
> email: marten@dmfs.org
> 
> Managing Director: Marten Gajda
> Registered address: Dresden
> Registered No.: AG Dresden HRB 34881
> VAT Reg. No.: DE303248743
> 
> _______________________________________________
> websec mailing list
> websec@ietf.org
> https://www.ietf.org/mailman/listinfo/websec
> 
> 
> 
> _______________________________________________
> websec mailing list
> websec@ietf.org
> https://www.ietf.org/mailman/listinfo/websec
>

v2.23.0 | Report a Bug | By Email