From: alicexbt <alicexbt@protonmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] BGP hijacking on Bitcoin p2p network
Date: Thu, 09 Jun 2022 18:24:03 +0000 [thread overview]
Message-ID: <dEY4dMW9awXrHkDOv-V7OSpjaPXHONVAaCSQ63gq1lQN0jWqJfeSoB4zlAwTn5I7J2L_YmzwcL_O6SbY9MBPnG845D8wmkauQzXeaD7VykA=@protonmail.com> (raw)
Hi Bitcoin Developers,
Based on this [answer][1] from 2014, bitcoin nodes are vulnerable to BGP hijacking. There was an incident in March 2022, twitter prefix was hijacked and details are shared in 2 blog posts:
https://isc.sans.edu/diary/rss/28488
https://www.manrs.org/2022/03/lesson-learned-twitter-shored-up-its-routing-security/
'nusenu' had written an article about Tor network being vulnerable to BGP hijacking attacks: https://nusenu.medium.com/how-vulnerable-is-the-tor-network-to-bgp-hijacking-attacks-56d3b2ebfd92
After doing some research I found that RPKI ROA and BGP prefix length can help against BGP hijacking attacks. I checked BGP prefix length and RPKI ROA for first 10 IP addresses returned in `getnodeaddresses` in bitcoin core and it had vulnerable results.
https://i.stack.imgur.com/KD7jH.png
Has anyone written a detailed blog post or research article like nusenu? If not I would be interested to write one in next couple of weeks?
Looking for some "technical" feedback, links if this was already discussed in past with some solutions.
[1]: https://bitcoin.stackexchange.com/a/30305/133407
/dev/fd0
Sent with Proton Mail secure email.
next reply other threads:[~2022-06-09 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 18:24 alicexbt [this message]
2022-06-10 6:44 ` [bitcoin-dev] BGP hijacking on Bitcoin p2p network Elias Rohrer
2022-07-05 20:30 ` alicexbt
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='dEY4dMW9awXrHkDOv-V7OSpjaPXHONVAaCSQ63gq1lQN0jWqJfeSoB4zlAwTn5I7J2L_YmzwcL_O6SbY9MBPnG845D8wmkauQzXeaD7VykA=@protonmail.com' \
--to=alicexbt@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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