All the recent exploits in the open-source Bitcoin ecosystem make me wonder about the future of FOSS development.
In its current form, it’s too exposed. It isn’t only well-intentioned people watching the code. Attackers now scan GitHub for vulnerabilities and exploit them before maintainers can ship a fix.
Developers are under unhealthy pressure. They know the enemy is watching and will abuse any crack left in the code, and they’ll do it lightning fast.
That’s why they have to improvise with private encrypted side channels to talk about bugs, and with patches released before the code itself, so users can update without broadcasting the scope of the changes.
I think this is going to be one of the hardest problems for the space. In this case, transparency doesn’t work in our favor.
We are in the middle of the Great Hardening, and I am still convinced open source is the right way to build software. We just have to stay one step ahead of attackers and have the right tools to make the code literally bulletproof before it ever reaches production.
In its current form, it’s too exposed. It isn’t only well-intentioned people watching the code. Attackers now scan GitHub for vulnerabilities and exploit them before maintainers can ship a fix.
Developers are under unhealthy pressure. They know the enemy is watching and will abuse any crack left in the code, and they’ll do it lightning fast.
That’s why they have to improvise with private encrypted side channels to talk about bugs, and with patches released before the code itself, so users can update without broadcasting the scope of the changes.
I think this is going to be one of the hardest problems for the space. In this case, transparency doesn’t work in our favor.
We are in the middle of the Great Hardening, and I am still convinced open source is the right way to build software. We just have to stay one step ahead of attackers and have the right tools to make the code literally bulletproof before it ever reaches production.