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

Donald Eastlake <d3e3e3@gmail.com> Wed, 26 December 2018 01:04 UTC

Return-Path: <d3e3e3@gmail.com>
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 10CE5130E63 for <babel@ietfa.amsl.com>; Tue, 25 Dec 2018 17:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 A6bWjyK64bwU for <babel@ietfa.amsl.com>; Tue, 25 Dec 2018 17:04:31 -0800 (PST)
Received: from mail-it1-x12a.google.com (mail-it1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11375130E62 for <babel@ietf.org>; Tue, 25 Dec 2018 17:04:31 -0800 (PST)
Received: by mail-it1-x12a.google.com with SMTP id x124so24251153itd.1 for <babel@ietf.org>; Tue, 25 Dec 2018 17:04:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aRZ5ofRnPy3mnBG2oSeKqXPy468X9KWnNdPTbT9N0eY=; b=i4R+ZqQ5pd1aG69qirC/oE7eJ9iOXqRbUvV7AuRtYHGvALNnhA43H6Mej93hkhZufh WXRs3wrNM9gnHI60AP5HO5WYiwycYoqQxkEOLRT54oNKhTQyWOytwmT60PQTNXHdFy+w /F+FyvAsunhmzu5HaDhRYk1X+oqqkzfwJ6QF28cjX3Pd5XHxwrqs8fzfpE7pmgTcet/g OPOhc4DbsjcIzyF5psLDkLHHMuaAlPt3YZ93Id0eVFdAR5TQEuTOb2lZbCjWbTr4t5h/ mIRfwmOE/ZqDs5DzLsTPVQHBxoLDmN+qQ8A+P/l+e7Hm1iIae4anYk0UPtgGBevS1SS+ y24w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aRZ5ofRnPy3mnBG2oSeKqXPy468X9KWnNdPTbT9N0eY=; b=mwvCHIoX7mHltxLY7HsrzBsfKsmRuA/Ve54Bq9tKbRpsyF0SMpMw5Edp4bMy57sCTG lB7xz2KyvobwCHWVPfZPweuo3LDOSzlOzUGrwHD+3nDDPHEJLIb7RREJqzR20wo6RELC S76/a9KEq+Gd2PcKMQWiMWJpLUwMSLroPv4qnpMHgh2AhraCU4Dk5POpRPekFexqvf2E 8kc891QH2imK9v/u1FTxsUqju9JiOJGFJOOf1vuktt3j7g1NHVG3XH63kMlgAI5SYrrO hTlZdjuB2fgz/Ml3PBWZM2J8RIf4SXwIlXTQDBLEav8b3Rn/KibOcLWEeWCLnpOk9XvV XYqw==
X-Gm-Message-State: AA+aEWaouqbItrgmpADif74w/4K6Uuwm3Pzh6xEfeQS3sLEG6zspYySt jg6DBlDT9n5Otp0J6N4fH/25bkxPjcKxOwmHk9U=
X-Google-Smtp-Source: ALg8bN7aabb2Kx+cc19NWbKFEZV58CHoPpmk+jWLyg9c8ihIInaFo75ug7dkd2qmicmIPdoWR/AySLxcUbQqGa89MIQ=
X-Received: by 2002:a24:6e88:: with SMTP id w130mr10961848itc.103.1545786270210; Tue, 25 Dec 2018 17:04:30 -0800 (PST)
MIME-Version: 1.0
References: <CAA93jw7J+7XsJnFeOg_g33qE7yF64VncNkEiw8AL_GFP2-QfGg@mail.gmail.com> <87d0ptle9k.wl-jch@irif.fr> <87va3lfrj4.fsf@toke.dk> <877eg0ugd1.wl-jch@irif.fr> <87h8f2fuh3.fsf@toke.dk>
In-Reply-To: <87h8f2fuh3.fsf@toke.dk>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 25 Dec 2018 20:04:18 -0500
Message-ID: <CAF4+nEG_+uGsFZF9S7m4epHT-DtZ4pUzntzL8cuwRwYt+j2Xvw@mail.gmail.com>
To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= <toke@toke.dk>
Cc: Juliusz Chroboczek <jch@irif.fr>, Babel at IETF <babel@ietf.org>, babel-users <babel-users@lists.alioth.debian.org>
Content-Type: multipart/alternative; boundary="00000000000088e28f057de2699c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/o8zho4zHfIHoQGGch7c6WDcoG6w>
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: Wed, 26 Dec 2018 01:04:36 -0000

If you need a KDF, I recommend RFC 5869.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 1424 Pro Shop Court, Davenport, FL 33896 USA
 d3e3e3@gmail.com


On Mon, Dec 24, 2018 at 5:09 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> 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
>
> _______________________________________________
> Babel-users mailing list
> Babel-users@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/babel-users