To: bitcoin-dev@lists.linuxfoundation.org
References: <57A89EA3.4020101@jonasschnelli.ch>
	<57A8BCD9.7050402@AndySchroder.com>
	<CAAS2fgQ1LZO=A-bqkJUod2og006iqWJn7RnyWc5cYnnnUq5MHg@mail.gmail.com>
	<57A8C76D.1080405@AndySchroder.com> <57A9AA1E.9050302@jonasschnelli.ch>
From: Jonas Schnelli <dev@jonasschnelli.ch>
Message-ID: <57ADC563.5090107@jonasschnelli.ch>
Date: Fri, 12 Aug 2016 14:47:31 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
	Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <57A9AA1E.9050302@jonasschnelli.ch>
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature";
	boundary="9tW64LQlBhNlFeuasgUWJIpH68NT7Il60"
Subject: Re: [bitcoin-dev] Authentication BIP
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--9tW64LQlBhNlFeuasgUWJIpH68NT7Il60
Content-Type: multipart/mixed; boundary="jv8pKWgG6MkFVrakPNFELj2aVlRQxknC0"
From: Jonas Schnelli <dev@jonasschnelli.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <57ADC563.5090107@jonasschnelli.ch>
Subject: Re: [bitcoin-dev] Authentication BIP
References: <57A89EA3.4020101@jonasschnelli.ch>
 <57A8BCD9.7050402@AndySchroder.com>
 <CAAS2fgQ1LZO=A-bqkJUod2og006iqWJn7RnyWc5cYnnnUq5MHg@mail.gmail.com>
 <57A8C76D.1080405@AndySchroder.com> <57A9AA1E.9050302@jonasschnelli.ch>
In-Reply-To: <57A9AA1E.9050302@jonasschnelli.ch>

--jv8pKWgG6MkFVrakPNFELj2aVlRQxknC0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

> Yes. I think this limitation could be removed.
> A responding node can have =96 in theory =96 multiple identity-keys per=

> network interface (network interfaces is also confusing, because you
> could run multiple bitcoind instances on the same interface with
> different ports).
>=20
> The BIP should just make clear, that it is probably wise, to use
> different identity-keys for each network interface (ipv4, v6, tor).
>=20

I have updated that part of the BIP

-----------
Each peer can configure multiple identity-keys (ECC, 32 bytes). Peers
should make sure, each network interface (IPv4, IPv6, tor) has its own
identity-key (otherwise it would be possible to link a tor address to a
IPvX address).
The identity-public-key(s) can be shared over a different channel with
other node-operators (or non-validating clients) to grant authorized acce=
ss.
-----------

https://github.com/bitcoin/bips/compare/master...jonasschnelli:2016/07/au=
th_bip?expand=3D1

</jonas>


--jv8pKWgG6MkFVrakPNFELj2aVlRQxknC0--

--9tW64LQlBhNlFeuasgUWJIpH68NT7Il60
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXrcVjAAoJECnUvLZBb1PsiXAQALca3O7LVyEVXq9zvx16HMVV
FkzvSwuSDW7/0VL9DryzeKh7t9PlY6278GlhLKU763aghMk/AOzBeOSKSOIH0fcb
DKdxI1GPApu2wRPbR4VeP7gJT22gKHO8dhekQH/cOfmeZyw0D9SqutWqZkvX3UVh
1jl+tHyvGngjuuLQAisXmNtC0n40nsULzUpdGcW2S0SDSb5GfTejYY6tpUjlt4Sh
drOL0bAgKtibnk2s2K7MO6uYVYtB+OahjrN/dq0BZAugrT2Vq05CtbpUAqo0nd/X
Zvm8VXNgR9Wn2Fg9DeXU/fL6IA6p8elHYG6CWtZJ4+ttJz1cpOKBjD80hp0+BwuJ
r2rkM2d9oi15YmvupauE18eJtBG7xEMUW0gV2mAAIb7V4SmfCFmn29BZbxuyiTIa
Aes3j8+wcShqqfVPlu7iO0gZ5ZVP/xu7MAg3Pxr6Rq2GEOrbdl0NRtktRqNUON28
iDr2KyV7gIohcneNYD4lPajGAyLf6hi/NztBcbzkNDMWew2lfj8aKE1cuL+2FydC
y13zuqQDdndWjYfXJNN2RmANwxsedfbCCPqc1GPTOby4tXBZvOmfwb+UwDlcPmog
1m07gSGz1SLs+LdBexVlM+Z4gnuOUwx8JBO3AtTyqajQ1ZmI43dGAOK7TzEzdRok
EF5uOBtMk/Sn4HPmuKcb
=JNz/
-----END PGP SIGNATURE-----

--9tW64LQlBhNlFeuasgUWJIpH68NT7Il60--