From: Elias Rohrer <btcdevml@tnull•de>
To: alicexbt <alicexbt@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BGP hijacking on Bitcoin p2p network
Date: Fri, 10 Jun 2022 08:44:05 +0200 [thread overview]
Message-ID: <31411E6C-B1BF-45B7-848A-0AC8ECDFFCB3@tnull.de> (raw)
In-Reply-To: <dEY4dMW9awXrHkDOv-V7OSpjaPXHONVAaCSQ63gq1lQN0jWqJfeSoB4zlAwTn5I7J2L_YmzwcL_O6SbY9MBPnG845D8wmkauQzXeaD7VykA=@protonmail.com>
Hi alicexbt,
Routing attacks have actually been studied quite a bit in literature.
You may be interested in the research articles of Maria Apostolaki et al.[1,2], Muoi Tran et al.[3], and related works.
Best,
Elias
[1]: https://arxiv.org/pdf/1605.07524.pdf
[2]: https://arxiv.org/pdf/1808.06254.pdf
[3]: https://allquantor.at/blockchainbib/pdf/tran2020stealthier.pdf
On 9 Jun 2022, at 20:24, alicexbt via bitcoin-dev wrote:
> 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.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2022-06-10 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 18:24 alicexbt
2022-06-10 6:44 ` Elias Rohrer [this message]
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=31411E6C-B1BF-45B7-848A-0AC8ECDFFCB3@tnull.de \
--to=btcdevml@tnull$(echo .)de \
--cc=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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