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

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

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 781CB129508 for <>; Mon, 24 Dec 2018 14:09:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BeVKTh7p21y4 for <>; Mon, 24 Dec 2018 14:09:04 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4530512896A for <>; Mon, 24 Dec 2018 14:09:04 -0800 (PST)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; 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 <>
Cc: Dave Taht <>, babel-users <>, Babel at IETF <>
In-Reply-To: <>
References: <> <> <> <>
Date: Mon, 24 Dec 2018 23:08:56 +0100
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <>
Subject: Re: [babel] [Babel-users] BASE64 and hex encoding HMAC keys for user presentation
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 24 Dec 2018 22:09:05 -0000

Juliusz Chroboczek <> 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 :)