Re: [openpgp] Mining protection in fingerprint schemes
Phillip Hallam-Baker <phill@hallambaker.com> Mon, 11 April 2016 12:04 UTC
Return-Path: <hallam@gmail.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A649D12EC29 for <openpgp@ietfa.amsl.com>; Mon, 11 Apr 2016 05:04:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 ZyhS5ZbSZuQU for <openpgp@ietfa.amsl.com>; Mon, 11 Apr 2016 05:04:23 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 B502912EC1C for <openpgp@ietf.org>; Mon, 11 Apr 2016 05:04:22 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id c126so153468578lfb.2 for <openpgp@ietf.org>; Mon, 11 Apr 2016 05:04:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to; bh=qCIKpw0nllaI2DZFGjwJnmtef9jUSpiS5zHOJpHBhlY=; b=M1FMRmRpsF7O3VEhKji/QKqd1gMYdyT5UHnu5QdhjPtWJ80T4B3TlwcwQHqGezzzGF INk1SSnaXQhFYKiGnfUMNW2DqFEeGgck/Kiz48o2QiWOH5IOIgHPTCHmUsicQVPVGAd/ i5GgihfEl54FH2YKZEJ3IhAAce0pdyx3IGT3f0r5ER8+zm7ZL12jgbI905HQ/60pKqmt P3cw78jo9g4LmpdhV/dUlgmn6cXgb9UX+HM7ymn2fHOS2yI5IlwgRnnnKjnCyW+3c/eg 170uNsN40Q5H+aeld+K5w0Q1sC022Ol58MjXAsesaL4yD3ecad4RnvDXlcnINxc41QDk WbGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to; bh=qCIKpw0nllaI2DZFGjwJnmtef9jUSpiS5zHOJpHBhlY=; b=ceHIrhIrMYdNCmwoaDhn74AiCBUiXwTLlvHIU7eOJU3MUSerznB6OXfzQlcO92G6Hm xK2LBkTrM6o+9jzb/NTjs+CUy+IFIiyPRhe79pzgha4GktJb5jCdbHJH/xh4rJ1vX01Y AJqPBDJdGkc9jeWsZW739pMGf2DTcOsYGwQev4EbLhf7hkH9Z9F4dq7wGp6SgoK8lyWn yh68xZkeUbDKvBszKke9PDB2tJhzesZmnRNqh6mZ31h0SPy85agFtuu7ih8uAUKpwJye PfT+oMldLVJZpmhR0ONrFJuZXaS0xk0i+4GbGDrIQw9oX3x+ffAz3dBKK7fmePELIFL5 N0kA==
X-Gm-Message-State: AD7BkJInxf38Gl9jQ1RBMyQCQOjehpXJg7JIVD/QxlfjqwNsohTW1vi/3JjCcXVTMBfj+rp3pwzPJikTy+kmvQ==
MIME-Version: 1.0
X-Received: by 10.112.10.109 with SMTP id h13mr6324576lbb.58.1460376260842; Mon, 11 Apr 2016 05:04:20 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.151.67 with HTTP; Mon, 11 Apr 2016 05:04:20 -0700 (PDT)
In-Reply-To: <20160410211449.GA12408@littlepip.fritz.box>
References: <4C08CDDD-4C06-41AD-9797-7DD6F08ECD06@gmail.com> <2AA5B912-0AE6-4722-8BC7-66E37559C0B1@callas.org> <D17B23A3-633F-4E4E-BC14-69ED6060F357@gmail.com> <6E221A61-7AB2-4E0B-B64D-60F210A0131F@callas.org> <E9A5B4B3-0EEC-4E86-8CEC-6680A24BE44F@gmail.com> <0D7A75AB-74C6-40E9-87C5-BA6F05FCDBF7@callas.org> <87oa9jo5sp.fsf@alice.fifthhorseman.net> <9C461E78-DC60-4B9D-A0DF-170F4759A57D@callas.org> <5E793A3D-128D-470A-8DF7-50827F39E02F@gmail.com> <20160410211449.GA12408@littlepip.fritz.box>
Date: Mon, 11 Apr 2016 09:04:20 -0300
X-Google-Sender-Auth: p4yFYIi8mPUeUPO-YDo5Ziq7F9Q
Message-ID: <CAMm+Lwgqbv4S94M2xYua4gAOWFxr_Kt5y6X8tQEWkaf7weeH+A@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: IETF OpenPGP <openpgp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/HnMkkqy7Q0LgkGvYRyIK_U4Scxc>
Subject: Re: [openpgp] Mining protection in fingerprint schemes
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Apr 2016 12:04:24 -0000
Fingerprints are used for two purposes. 1) To define a trust anchor. 2) To verify that a purported trust anchor is correct Only the first of these requires the ability to enter the fingerprint at a keyboard. The most efficient way that is compliant with existing keyboards etc. is Base32. While not all keyboards have latin characters, there is an effective limit on the number of keys, screen real estate etc. The second requires only the ability to compare the fingerprints. Here the PGP word scheme shows a more efficient approach, using an alphabet of effectively 256 glyphs that are phonetically distinct words. But we need not stop at 256 code points. We could just as easily use Base65536 or Base1048576 alphabets. Comparing pictures, words, whatever. Words are my favorite as they allow keys and/or fingerprints to be encoded in messages. Lets say that our alphabet has a restriction that the words have to be 4 letters or more. A 128 bit key in base65536 requires 8 words, lets say these are boat syringe lawnmower noise suitcase horse advice loaf. You can make up a cryptic phrase to encode the key steganographically. Fix the boat, use a syringe. The lawnmower noise is bad. etc. The downside to word dictionaries is that they are language specific. Images are better. For the Mesh, I plan to eventually use vocabularies of curated images. Get a bunch of 256 volunteers, give them the task of curating collections of 256 picture themes each to find pictures that are visually distinct. I have more here: https://datatracker.ietf.org/doc/draft-hallambaker-udf/
- [openpgp] Mining protection in fingerprint schemes Bryan Ford
- Re: [openpgp] Mining protection in fingerprint sc… Jon Callas
- Re: [openpgp] Mining protection in fingerprint sc… Bryan Ford
- Re: [openpgp] Mining protection in fingerprint sc… Jon Callas
- Re: [openpgp] Mining protection in fingerprint sc… Bryan Ford
- Re: [openpgp] Mining protection in fingerprint sc… Peter Gutmann
- Re: [openpgp] Mining protection in fingerprint sc… Robert J. Hansen
- Re: [openpgp] Mining protection in fingerprint sc… Jon Callas
- Re: [openpgp] Mining protection in fingerprint sc… Daniel Kahn Gillmor
- Re: [openpgp] Mining protection in fingerprint sc… Jon Callas
- Re: [openpgp] Mining protection in fingerprint sc… Peter Gutmann
- Re: [openpgp] Mining protection in fingerprint sc… Bryan Ford
- Re: [openpgp] Mining protection in fingerprint sc… Vincent Breitmoser
- Re: [openpgp] Mining protection in fingerprint sc… Phillip Hallam-Baker
- Re: [openpgp] Mining protection in fingerprint sc… Vincent Breitmoser
- Re: [openpgp] Mining protection in fingerprint sc… Daniel Kahn Gillmor
- Re: [openpgp] Mining protection in fingerprint sc… Phillip Hallam-Baker
- Re: [openpgp] Mining protection in fingerprint sc… Hilarie Orman
- Re: [openpgp] Mining protection in fingerprint sc… Peter Gutmann
- Re: [openpgp] Mining protection in fingerprint sc… brian m. carlson
- Re: [openpgp] Mining protection in fingerprint sc… Daniel Kahn Gillmor
- Re: [openpgp] Mining protection in fingerprint sc… Werner Koch
- Re: [openpgp] Mining protection in fingerprint sc… Derek Atkins
- Re: [openpgp] Mining protection in fingerprint sc… Bryan Ford
- Re: [openpgp] Mining protection in fingerprint sc… Bryan Ford
- Re: [openpgp] Mining protection in fingerprint sc… Peter Gutmann