Re:OpenBSD system-call-origin verification
by gok on Sunday December 22, 2019 @09:36PM
(#21861106)
It's totally acceptable to write to libc in something other than C, or in fact to write libc itself in something other than C.
[ Parent
| on HN ]
Re:OpenBSD system-call-origin verification
by pjmlp on Monday December 23, 2019 @02:50AM
(#21862106)
Example, Microsoft has rewritten their C standard library in C++ with extern "C" entry points.
Re:OpenBSD system-call-origin verification
by nineteen999 on Tuesday December 24, 2019 @11:55AM
(#21873260)
Yes. Microsoft have made a number of silly mistakes with respect to OS design, which has cost them the server space outside of authentication for your and my lifetime. Bloat is not the answer to either security or performance problems.
Re:OpenBSD system-call-origin verification
by pjmlp on Friday December 27, 2019 @07:59AM
(#21891074)
Quite the contrary, I admire Microsoft for being one of the first companies to start driving C away from our IT stacks.
Thankfully Apple, Google, IBM and Unisys seem to be on the same boat.
Re:OpenBSD system-call-origin verification
by saagarjha on Sunday December 22, 2019 @09:51PM
(#21861168)
And llvm-libc may be one such implementation: https://llvm.org/docs/Proposals/LLVMLibC.html
Re:OpenBSD system-call-origin verification
by nineteen999 on Tuesday December 24, 2019 @11:07AM
(#21872900)
That's a pipe dream, not an implementation. Let's wait until it actually happens before getting too excited, and then we be actually able to evaluate the drawbacks.
> Current Status - llvm-libc development is still in the planning phase.