path: root/10/2d0a407813bc3ef5a4d1198ea768a29e749f0e

Return-Path: <clem.ds@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id E5D2D360
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 21 Jul 2015 08:42:13 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yk0-f176.google.com (mail-yk0-f176.google.com
	[209.85.160.176])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0A6ECDE
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 21 Jul 2015 08:42:13 +0000 (UTC)
Received: by ykay190 with SMTP id y190so159659883yka.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 21 Jul 2015 01:42:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to
	:content-type; bh=JvwRQllpsKZSSxFWS4AWlUwGrnYfdkeRyt+UtLVtkX4=;
	b=LMz8YpWNRzPYdqQQFb896BkT06hXSjQfbjlBAKBx1rJcq33yqrIloDWaReO/NNfAk1
	dHjU9x1lAllx+YoCGvzHr54GPI2ivnQMAWE+/JsyZxM6Bfq/Uoq5QdR/7dwJUDK+UstY
	YrzrdlTnuEztttNvBN5Q2ECi8uTgF7JasSc6vs9fQSb4LQNEfQIhcA5v87qxAx8lSG7H
	21aZfsdwk0V0z65vU/pjY+D3LN00X4WsPLahfL/FD+FSo6d6jG+R4Jx8afxwhkQc2zE8
	cIMHPNduufgpamR5Sez8dtonwCWqHfL6CwHKy5e2WDJeSMZU2QSiXQGkK3qPgpfDrI0U
	ifTw==
X-Received: by 10.13.213.3 with SMTP id x3mr32683950ywd.156.1437468132249;
	Tue, 21 Jul 2015 01:42:12 -0700 (PDT)
MIME-Version: 1.0
References: <CA+w+GKRRfT=8xALsVMqEUAZWzd87Lf4HqFPuDigatY+nHzafQQ@mail.gmail.com>
	<mokvc1$p4m$1@ger.gmane.org>
In-Reply-To: <mokvc1$p4m$1@ger.gmane.org>
From: =?UTF-8?Q?Cl=C3=A9ment_Elbaz?= <clem.ds@gmail.com>
Date: Tue, 21 Jul 2015 08:42:02 +0000
Message-ID: <CAP63atZdnDjdvtwDVq36uBO3TRch9e1=6ueRgicKxm_dRs2b7w@mail.gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>,
	bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a114fc15a6616f6051b5ea134
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] QR code alternatives (was: Proposal: extend bip70
 with OpenAlias)
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2015 08:42:14 -0000

--001a114fc15a6616f6051b5ea134
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

As a side note, you may be interested about the 2D-Doc, which is a new
French standard used to protect documents such as address proofs or
invoice. I've been involved with it closely at work.

Every 2d-Doc include an ECDSA signature inside a 2D barcode, the key being
that the barcode is a Datamatrix and not a QR code.

If any of you can read French, the technical specification of the standard
can be found here ::
https://ants.gouv.fr/content/download/516/5665/version/4/file/ANTS_2D-Doc_C=
ABSpec_v2.0.1_erratum.pdf

Basically, a short summary of the protected document is encoded inside the
barcode, followed by an ECDSA signature of the summary (still in the
barcode). The signature is done by an official, government-approved 2D-Doc
emitter. The 2D-Code contains a short reference (a few bytes) to designate
which emitter signed it, and then you can lookup the 2D-Doc TSL supplied by
the French government to get all the X509 Certificates from every emitters
you are interested in, in order to check the signature.

While 2D-Doc solve a very different problem than Bitcoin + BIP70, you may
be interested in knowing about it as hundred of thousands of them have been
emitted successfully while solving one of the problem you face : embedding
an ECDSA signature inside a 2D barcode.

Thank you for your time,

Cl=C3=A9ment Elbaz

Le mar. 21 juil. 2015 =C3=A0 10:20, Andreas Schildbach via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> a =C3=A9crit :

> Hmm, the advanced QR code standards are perhaps even useful if we don't
> change anything about BIP7x. Because if we can cram more data without
> loosing scanning performance this maybe means also we can stay with the
> data we have but improve scanning?
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--001a114fc15a6616f6051b5ea134
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As a side note, you may be interested about the 2D-Doc, wh=
ich is a new French standard used to protect documents such as address proo=
fs or invoice.=C2=A0I&#39;ve been involved with it closely at work.<div><br=
></div><div>Every 2d-Doc include an ECDSA signature inside a 2D barcode, th=
e key being that the barcode is a Datamatrix and not a QR code.</div><div><=
br></div><div>If any of you can read French, the technical specification of=
 the standard can be found here ::=C2=A0<a href=3D"https://ants.gouv.fr/con=
tent/download/516/5665/version/4/file/ANTS_2D-Doc_CABSpec_v2.0.1_erratum.pd=
f">https://ants.gouv.fr/content/download/516/5665/version/4/file/ANTS_2D-Do=
c_CABSpec_v2.0.1_erratum.pdf</a></div><div><br></div><div>Basically, a shor=
t summary of the protected document is encoded inside the barcode, followed=
 by an ECDSA signature of the summary (still in the barcode). The signature=
 is done by an official, government-approved 2D-Doc emitter. The 2D-Code co=
ntains a short reference (a few bytes) to designate which emitter signed it=
, and then you can lookup the 2D-Doc TSL supplied by the French government =
to get all the X509 Certificates from every emitters you are interested in,=
 in order to check the signature.</div><div><br></div><div>While 2D-Doc sol=
ve a very different problem than Bitcoin + BIP70, you may be interested in =
knowing about it as hundred of thousands of them have been emitted successf=
ully while solving one of the problem you face : embedding an ECDSA signatu=
re inside a 2D barcode.</div><div><br></div><div>Thank you for your time,</=
div><div><br></div><div>Cl=C3=A9ment Elbaz</div><div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr">Le=C2=A0mar. 21 juil. 2015 =C3=A0=C2=A010:20, And=
reas Schildbach via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.lin=
uxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</=
a>&gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hmm, the=
 advanced QR code standards are perhaps even useful if we don&#39;t<br>
change anything about BIP7x. Because if we can cram more data without<br>
loosing scanning performance this maybe means also we can stay with the<br>
data we have but improve scanning?<br>
<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div></div></div>

--001a114fc15a6616f6051b5ea134--