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

Dave Taht <dave.taht@gmail.com> Sat, 01 December 2018 20:11 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 EEE28130E35 for <babel@ietfa.amsl.com>; Sat, 1 Dec 2018 12:11:23 -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 PaB6D8X4t9-S for <babel@ietfa.amsl.com>; Sat, 1 Dec 2018 12:11:22 -0800 (PST)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 9706B130DFE for <babel@ietf.org>; Sat, 1 Dec 2018 12:11:22 -0800 (PST)
Received: by mail-qt1-x834.google.com with SMTP id d19so9726189qtq.9 for <babel@ietf.org>; Sat, 01 Dec 2018 12:11:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=hRvRzO64uiF5Sq6qff3D3M+BQ9vPhXBt0p0VDBFK/4M=; b=buEWiuBy2zo+QpO8xpQrZNhTzoWe6zAWkqGSonNTLkksLFTCdlZmoPwT/VnU7HX//K pDz2ACuNw2uNjJ+eg3O7suP7m6GpuAeP9lNnCslTyg/Retmt79Fi3/+zSnL8jltOPndf RpI7r8bkrLpEnT19THG2Yh2jVyRzhJ7FiV0M3TP8zueg28gh+vLgNj2VI+CmQrNoXrk+ FGvmduDkFkoNLiFnFhN9wuTth78ovpLDln1WT1U/9F81SIbSUSIfNfEh7oOLW9Sb6pXo wslja0Slr1MusgERs3DZQq2wSfo9INN4h1Mypf77duh17jadDtfGVkvXPR89PwCw+Wuz EKFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=hRvRzO64uiF5Sq6qff3D3M+BQ9vPhXBt0p0VDBFK/4M=; b=fViLmOi95dkqlY/hs3mv8hQ9LUOGPtdXEHboEj6AkH1BsEEREl5rWyeP/9bZJnHXuk yLaPW6+/G6mtDp9rKdgY8XPmlKw8sYooBym4XKnS3chyebx8of64f57G0IbmerWF/LZU BLVDRqzSMeGuKXAkOtkpuLwK7bfieUTW49pfF2xTMMmcrMWiUGHAPXRN2Jms2Vpf3D2J ccGhSLTbqcY62ws/rN/IPkQ8MfYJTpj+cT11QFfmS6VcmTW7ZcTaJBbyRMX5FT9J68+Y r2neiSo4xzsBS0I3M478aeI5XxyjhQ/HShsqEfeTeU1JaJp9jTnUate8yy2WO2T7zVnE pghw==
X-Gm-Message-State: AA+aEWYrANEPcjhqVplpjoPSt+xGyTGKmSxMJmHF5uDO3ZtPkD6zGnsl 1npOTPCZjgplLd2ibAnPv+ptcpcy6I108Di8DT8=
X-Google-Smtp-Source: AFSGD/WWU1I8fN34x+YwzT3rmCkKszwNjL7koHsI7n1bDD288w0cgxZIB/G8IDha0CZVi54mP6mcCqJZ46YG7wba6As=
X-Received: by 2002:a0c:a402:: with SMTP id w2mr10548449qvw.129.1543695081651; Sat, 01 Dec 2018 12:11:21 -0800 (PST)
MIME-Version: 1.0
From: Dave Taht <dave.taht@gmail.com>
Date: Sat, 1 Dec 2018 12:11:09 -0800
Message-ID: <CAA93jw7J+7XsJnFeOg_g33qE7yF64VncNkEiw8AL_GFP2-QfGg@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/xoC6eAsF5ulL2SrOYSWefeDaro8>
Subject: [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:11:24 -0000

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


-- 

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