From: Jonas Schnelli <dev@jonasschnelli.ch>
To: Tom Zander <tomz@freedommail.ch>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Unique node identifiers (and BIP150)
Date: Wed, 8 Mar 2017 22:31:01 +0100 [thread overview]
Message-ID: <FBFEE1B5-9243-45DA-A8F6-1449591DCAB6@jonasschnelli.ch> (raw)
In-Reply-To: <18390846.ckRIaq9dAb@strawberry>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
Hi Tom
> Do you know the trick of having an open wifi basestation in a public street
> and how that can lead to tracking? Especially if you have a network of them.
> The trick is this; you set up an open wifi base station with a hidden ssid
> and phones try to connect to it by saying “Are you ssid=xyz?”
> This leads the basestation to know that the phone has known credentials with
> another wifi that has a specific ssid. (the trick is slightly more elaborate,
> but the basics are relevant here).
>
> Your BIP is vulnarable to the same issue, as a node wants to connect using
> the AUTHCHALLENGE which has as an argument the hash of the person I’m trying
> to connect with.
This thread is not about BIP150/151.
The hash includes the encryption session which makes it impossible to distinct identities.
>
> Your BIP says "Fingerprinting the requesting peer is not possible”.
> Unfortunately, this is wrong. Yes the peer is trivial to fingerprint. Your
> hash never changes and as you connect to a node anyone listening can see you
> sending the same hash on every connect to that peer, whereever you are or
> connect from.
Not true. The hash includes the encryption session which is based on a ephemeral ECDH/HKDF per connection-session.
Have you read the BIP?
</jonas>
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-03-08 21:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 16:04 [bitcoin-dev] Unique node identifiers John Hardy
2017-03-05 6:29 ` Marcel Jamin
2017-03-05 12:55 ` John Hardy
2017-03-05 13:27 ` Btc Drak
2017-03-05 13:57 ` John Hardy
2017-03-07 18:44 ` Eric Voskuil
2017-03-08 2:01 ` bfd
2017-03-08 19:47 ` Jonas Schnelli
2017-03-08 21:09 ` Eric Voskuil
2017-03-08 21:20 ` Jonas Schnelli
2017-03-08 23:12 ` Pieter Wuille
[not found] ` <6a5a6a8f-d689-260a-76a9-a91f6bda56c5@voskuil.org>
2017-03-09 1:55 ` Pieter Wuille
2017-03-09 11:01 ` Aymeric Vitte
2017-03-09 1:08 ` Eric Voskuil
2017-03-08 21:25 ` [bitcoin-dev] Unique node identifiers (and BIP150) Tom Zander
2017-03-08 21:31 ` Jonas Schnelli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FBFEE1B5-9243-45DA-A8F6-1449591DCAB6@jonasschnelli.ch \
--to=dev@jonasschnelli.ch \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=tomz@freedommail.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox