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.
Here's one reference: https://msrc-blog.microsoft.com/2019/07/18/we-need-a-safer-s...