News for hackers. Stuff that matters.
Re:Show HN: Mako – a full Bitcoin implementation in C by nynx on Monday November 15, 2021 @03:27PM (#29232255)
This is very impressive, but I’ll be honest, I wouldn’t want to expose any new software written in C to the internet.
Re:Show HN: Mako – a full Bitcoin implementation in C by kahlonel on Monday November 15, 2021 @10:07PM (#29236270)
Yeah it’s not like the browser you are using, the OS you have installed, or even the firmware of the keyboard you’re typing this on is written in C.
Re:Show HN: Mako – a full Bitcoin implementation in C by __vim__ on Tuesday November 16, 2021 @11:05AM (#29242125)
I feel this comment is misguided. Plenty of new code is written in C, particularly in the scientific computing space. If the code in question doesnt do lots memory management and expects the user to provide a memory block to be populated with values, then I see no issues. C code tends to be faster than other implementations even without optimizations. Moreover, lots of interpreted languages have good interoperability with C so a C compiled code can be called in many languages using simple high level interfaces.
Re:Show HN: Mako – a full Bitcoin implementation in C by 0xFFFFFFFFF on Monday November 15, 2021 @03:31PM (#29232296)
Can I ask you why? I mean, I know about memory safety and stuff, but it is that bad?
Re:Show HN: Mako – a full Bitcoin implementation in C by pizza234 on Monday November 15, 2021 @05:54PM (#29234027)
Independent researches (Microsoft/Mozilla) showed that around 70% of security vulnerabilities are caused by memory safety bugs. That's one heck of a "memory safety and stuff" :)

Here's one reference: https://msrc-blog.microsoft.com/2019/07/18/we-need-a-safer-s...

Re:Show HN: Mako – a full Bitcoin implementation in C by postalrat on Monday November 15, 2021 @06:54PM (#29234637)
"memory safety bugs" sounds pretty broad. What sort of vulnerability doesn't involve memory access?
Re:Show HN: Mako – a full Bitcoin implementation in C by UncleMeat on Tuesday November 16, 2021 @03:45PM (#29246153)
Something like SQL injection is a vulnerability that is not exploiting a memory error.
Re:Show HN: Mako – a full Bitcoin implementation in C by nynx on Monday November 15, 2021 @07:37PM (#29235020)
its “memory safety”, not “accesses memory”
Re:Show HN: Mako – a full Bitcoin implementation in C by shatteredspace on Monday November 15, 2021 @07:58PM (#29235207)
That reference and the original blog post where 70% was indicated is only dealing with security vulnerabilities in Microsoft's software, not everyone's.

So while other software that isn't Microsoft most certainly has memory safety bugs, this blog doesn't speak for those, only Microsoft's.

The only part that Mozilla is indicated is in reference to Rust.

Re:Show HN: Mako – a full Bitcoin implementation in C by syvolt on Monday November 15, 2021 @08:19PM (#29235407)
If one of the largest software companies around can't get memory safety right, it does make a guy start to think that maybe most people should avoid having to handle it if they can.
Re:Show HN: Mako – a full Bitcoin implementation in C by shatteredspace on Monday November 15, 2021 @08:45PM (#29235604)
I don't have a fully developed opinion on that, so I won't try to come up with one on the spot. My comment is purely because I felt the parent left out details about the blog post that should have been pointed out.
Re:Show HN: Mako – a full Bitcoin implementation in C by saagarjha on Tuesday November 16, 2021 @02:27AM (#29237856)
Google has done similar research on their codebases and found results in line with Microsoft’s.
Re:Show HN: Mako – a full Bitcoin implementation in C by roca on Monday November 15, 2021 @04:51PM (#29233279)
Yes it is.
Re:Show HN: Mako – a full Bitcoin implementation in C by jazzyjackson on Monday November 15, 2021 @03:36PM (#29232369)
I wouldn’t be too worried about a bitcoin node since the whole point is to stay in consensus with the rest of the network