Re: [babel] [Babel-users] BASE64 and hex encoding HMAC keys for user presentation
Juliusz Chroboczek <jch@irif.fr> Sun, 23 December 2018 20:40 UTC
Return-Path: <jch@irif.fr>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 628301277BB for <babel@ietfa.amsl.com>; Sun, 23 Dec 2018 12:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 TtjDDlv3qVo7 for <babel@ietfa.amsl.com>; Sun, 23 Dec 2018 12:40:18 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 B97B8126CC7 for <babel@ietf.org>; Sun, 23 Dec 2018 12:40:17 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id wBNKe8QV024784; Sun, 23 Dec 2018 21:40:08 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id BEF0493EB3; Sun, 23 Dec 2018 21:40:14 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id YiA8UuLdkG6R; Sun, 23 Dec 2018 21:40:12 +0100 (CET)
Received: from pirx.irif.fr (user-164-126-143-147.play-internet.pl [164.126.143.147]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 4FE1293EAE; Sun, 23 Dec 2018 21:40:11 +0100 (CET)
Date: Sun, 23 Dec 2018 21:40:10 +0100
Message-ID: <877eg0ugd1.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Toke Høiland-Jørgensen <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>, babel-users <babel-users@lists.alioth.debian.org>, Babel at IETF <babel@ietf.org>
In-Reply-To: <87va3lfrj4.fsf@toke.dk>
References: <CAA93jw7J+7XsJnFeOg_g33qE7yF64VncNkEiw8AL_GFP2-QfGg@mail.gmail.com> <87d0ptle9k.wl-jch@irif.fr> <87va3lfrj4.fsf@toke.dk>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 23 Dec 2018 21:40:09 +0100 (CET)
X-Miltered: at korolev with ID 5C1FF2A8.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5C1FF2A8.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 5C1FF2A8.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/H_ETTHzi5FUzuplJqAXJvqU6hD0>
Subject: Re: [babel] [Babel-users] BASE64 and hex encoding HMAC keys for user presentation
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Dec 2018 20:40:19 -0000
>> I think that the HMAC key should be generated automatically. I'd hope >> that any actual production deployment of HMAC would generate HMAC keys >> either randomly or by using a suitable KDF (or whatever the right acronym >> is) and distribute it automatically. > Should we pick a KDF? Not necessarily for the RFC, but at least try to > get compatibility between bird and babeld, so users can just input a > password and expect things to work? I think we might need more deployment experience before we can answer that. At this early stage, however, I wouldn't expect the master key to be distributed -- the KDF would be applied to the master key on a central node, and the derived secret is what gets distributed to the babeld and BIRD instances. So having a common syntax for the HMAC secret should be good enough. -- Juliusz
- [babel] BASE64 and hex encoding HMAC keys for use… Dave Taht
- Re: [babel] BASE64 and hex encoding HMAC keys for… Dave Taht
- Re: [babel] [Babel-users] BASE64 and hex encoding… Toke Høiland-Jørgensen
- Re: [babel] BASE64 and hex encoding HMAC keys for… Juliusz Chroboczek
- Re: [babel] [Babel-users] BASE64 and hex encoding… Toke Høiland-Jørgensen
- Re: [babel] [Babel-users] BASE64 and hex encoding… Juliusz Chroboczek
- Re: [babel] [Babel-users] BASE64 and hex encoding… Toke Høiland-Jørgensen
- Re: [babel] [Babel-users] BASE64 and hex encoding… Donald Eastlake