Re: [babel] [Babel-users] BASE64 and hex encoding HMAC keys for user presentation

Toke Høiland-Jørgensen <toke@toke.dk> Mon, 24 December 2018 22:09 UTC

Return-Path: <toke@toke.dk>
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 781CB129508 for <babel@ietfa.amsl.com>; Mon, 24 Dec 2018 14:09:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
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 BeVKTh7p21y4 for <babel@ietfa.amsl.com>; Mon, 24 Dec 2018 14:09:04 -0800 (PST)
Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (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 4530512896A for <babel@ietf.org>; Mon, 24 Dec 2018 14:09:04 -0800 (PST)
From: Toke Høiland-Jørgensen <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1545689340; bh=Bn/pWev2cS9AfV9cFPfRVR/TDKDhB0oMUMnjKhcFsII=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=MR+SUIODajSAWZrUJW1MbtaeA5d3JqamhepklERMbMGq/CFIV0xcEnre9PU+97Drt mWPFORbHL2pyqfGh7xgcHYhcu++Puy5szY3l9TljfWceBF1sCKNykqwr0a8qkdcy98 I5h7enEotNwl2RNj6QIpm7oWrv+6kwH+fiZd/3CHBa9gnI/ujp3B85fih4v8mR9ers M0o814S+MmcZSUuTekv9draIpxTB2sA7Cu34RIFdMqqhKAjRBywl7wUEoxZisMqqWi YrMq3c6LgpTC/1le73t+e+evy0LcExDB2kFzSe1eNxwHTtiIKOIm5Ta17QhmYB1y4B 0gVKTewx1/uzw==
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Dave Taht <dave.taht@gmail.com>, babel-users <babel-users@lists.alioth.debian.org>, Babel at IETF <babel@ietf.org>
In-Reply-To: <877eg0ugd1.wl-jch@irif.fr>
References: <CAA93jw7J+7XsJnFeOg_g33qE7yF64VncNkEiw8AL_GFP2-QfGg@mail.gmail.com> <87d0ptle9k.wl-jch@irif.fr> <87va3lfrj4.fsf@toke.dk> <877eg0ugd1.wl-jch@irif.fr>
Date: Mon, 24 Dec 2018 23:08:56 +0100
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87h8f2fuh3.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/O3b_3gShG2D1Fa4YXrxQLa-jIro>
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: Mon, 24 Dec 2018 22:09:05 -0000

Juliusz Chroboczek <jch@irif.fr> writes:

>>> 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.

Fair enough :)

-Toke