MORE C
Conversation
buffer overflows are unfiltered, undiluted by safety checks.
odds are 99.9% you've never tasted vulns this pure
2
1
28
3
7
genuinely terrifying few seconds while i tried to figure out how to get from "1 year ago" to an actual date for the article
1
4
It's actually real in addition to being trolling though.
Quote Tweet
Replying to @johnregehr @saleemrash1d and 2 others
It'll make sense if you look at the date, but it's also a real thing that's fully supported since libunit is a thing and usable for writing web apps in C and C++. They were basically just promoting libunit with trolling. IIRC, they listed assembly language support in the docs.
1
2
2
I think they got tired of people still using LAMP and decided outdo Apache by turning nginx into an in-process library/framework for a bunch of different languages. Basically the unikernel thing but with web servers. They just need to make it an OS now for maximum hype.
1
1
3
I don't think writing web apps in assembly is really that far off from how they like things. I mean, just look at their code. They don't believe in using the C standard library for the most part.
github.com/nginx/unit/tre
Maybe April Fools is cover to say what they think... hmm..
2
1
This is basically the nginx aesthetic in a few lines:
github.com/nginx/unit/blo
It gets scarier if you look at the context (reinventing threads / processes instead of using unshare).
If they were Rust programmers they'd never write a line of code without first using #![no_std].
I guess these might be better examples:
* github.com/nginx/unit/blo (artisan crafted userspace threads)
* github.com/nginx/unit/blo (magic)
* github.com/nginx/unit/blo (eeeeeee)
Free range organic Russian C. Probably a good codebase to apply UBSan... so much sketchy hand-rolled code.
1
1
6
Show replies