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

Dave Taht <dave.taht@gmail.com> Sat, 01 December 2018 20:12 UTC

Return-Path: <dave.taht@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 C1A48130E46 for <babel@ietfa.amsl.com>; Sat, 1 Dec 2018 12:12:34 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 mhcQSLudA8ba for <babel@ietfa.amsl.com>; Sat, 1 Dec 2018 12:12:33 -0800 (PST)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 C69F6130DFE for <babel@ietf.org>; Sat, 1 Dec 2018 12:12:32 -0800 (PST)
Received: by mail-qt1-x82e.google.com with SMTP id y20so9710085qtm.13 for <babel@ietf.org>; Sat, 01 Dec 2018 12:12:32 -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 :content-transfer-encoding; bh=xYpEr8jiBshU1QxfEbglfsuo2D1ThgLXnB4mz+yzVCs=; b=LorkE1HJxbOa7xUB3OqYtPQcUQFqNjioXw+fs8aDx5cSXYKVZw8SQGm5yL5NVgZP++ CBDi2zSBVJIXHIQ+qB9bK1OhZ+iRveRWlvhGt9ob3ORw1q91/Ws4OH/UDLqMrU2YItgO vfLUEsEpZ2Be++aPL1UZy6MbuFlZBaTnGtf/8xwKOSoNPMzwgHFIcOH9NOKzz1X86VX7 Ozf/tFYhWk0YAWGxP9qiwqgUFrakcyyL/APG+3cApxJQ3X6nxtLa5H11x+T0HzK3S1n7 h5cR7HvfRPsIJOeMaA/g4F82A979bilV8q8ZBewPp0bkKbHqZfYDwylJ6rjbH7NzTavn gUPw==
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:content-transfer-encoding; bh=xYpEr8jiBshU1QxfEbglfsuo2D1ThgLXnB4mz+yzVCs=; b=QFDwnZDci+UXR7FEdwqRUh9XNXMz3vmdwrbJzAd4Bg5bqLKpGViLoxDdB6o7ODBnVs wXhwSj8Yg2U7m4hL6nIUoUvOwOg7GhwESNl+qisvmtKf9dHRc/KVGNFC1w2CZSp8Bm1z oKORg3P7LtQd+qVeq2kKfqKvYYPsDb1R1LPGUzwYfg57AQwblW2zxn4baphWTwWVrg5Q cAwGhHwQP/cZWnyQ0h5y0iko0tVu8Z1f2s9xy6CsqwxHxQEn1RrcJeFu/H4LRBv6enpH H92BNXon0yfhytZYxa9k4jGndu3l+rn+T0TW/RNwW0RV4nqdcdAtIElBH8EDPuTfIq3f f2hA==
X-Gm-Message-State: AA+aEWbwnZe4yabnJP3uq2giNmPlJ3doQIiWyttoK88CAiPGkLF1Mu5b 1vhs4DxnVhXJXWiYKMvfMA0hLFKfGjg3fxdJDj1PeQ==
X-Google-Smtp-Source: AFSGD/WFLvrxrR0Rtxr5r1YkhVh4g8aE5/bckRuB76A+cfHGNlJL++6mX6TzZxNwU/hH7s/FVmbiTFyKlkX9ySdwhI8=
X-Received: by 2002:ac8:2e6a:: with SMTP id s39mr10343389qta.355.1543695151859; Sat, 01 Dec 2018 12:12:31 -0800 (PST)
MIME-Version: 1.0
References: <CAA93jw7J+7XsJnFeOg_g33qE7yF64VncNkEiw8AL_GFP2-QfGg@mail.gmail.com>
In-Reply-To: <CAA93jw7J+7XsJnFeOg_g33qE7yF64VncNkEiw8AL_GFP2-QfGg@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
Date: Sat, 1 Dec 2018 12:12:19 -0800
Message-ID: <CAA93jw6wq=BVc7a+oZpM8q4zGc_U6R+Xc23u31rw0FLcFmJ=cw@mail.gmail.com>
To: babel-users <babel-users@lists.alioth.debian.org>, Babel at IETF <babel@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/70HBOQHV14B-FhtFkQidjDDWXpY>
Subject: Re: [babel] 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: Sat, 01 Dec 2018 20:12:35 -0000

On Sat, Dec 1, 2018 at 12:11 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> I would like the bird and babel implementations to allow for and use
> BASE64 and hex encodings.
>
> This allows for a shorter, more human friendly representation of both
> cryptographically generated keys and the keys humans are more likely
> to remember and type without error. In the latter case, guidelines as
> to length, mixed case and punctuation would be useful.
>
> There are only so many hexadecimal jokes that are easy to remember,
> deadbeef being the most common. Requiring that a hex key be prefixed
> with 0x and that keys otherwise shown users
> be in base64 would make for an easier deployment, and keys like
> Get0ffMyLawnBadGuys and NSAdeliveryVAN easier on the eyes than the
> equivalent: 0x19eb747df3322dac2705a746bb2b and 0x35201d7a58af7abc9500
> and still allows for harder keys to be cryptographically generated by
> other tools, like IG/MmDjiVJW0+ojz32+4KDtVuGlJJKkhYEEEkpbwTkE=
>
> I do not off the top of my head know how much this compromises the
> dynamic range of a given key, but I would hope that being

easier on humans, it makes for an easier deployment.
>
> --
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740



-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740