>that means nobody can
unironically, yes.
that's how systems are designed. you'd know this if you weren't a toddler making bing bing wahoo widgets for worthless office wagies and their moronic children.
yes, barely.
you will also note that Linux use in critical systems is basically non-existent and to this day people post meme blogs about how they defeat linux ASLR, get a use-after-free primitive in some meme feature and make everyone seethe.
reminder to turn off io_uring or any new meme garbage feature in Linux. Not even Google uses most the new shit for a reason.
2 weeks ago
Anonymous
>autistic HRT-induced screeching
Thought so
2 weeks ago
Anonymous
no argument moron-kun?
I worked on some industrial shit in the past and the Linux component was just an overglorified DBMS with some basic user controlling features.
all the hard safety features are targeted outside of Linux. In fact, many customers still prefer the pre-Linux ARM shitbox devices to this day. Using Linux is fine and all, but you're a delusional troony if you think you should trust your life to an extremely complex, non-realtime operating system with a known history of merging extremely shitty code and still have very weak security programming practices or testing methodologies.
Linux is a dog shit code base and you're moronic. Note I'm not defending any of the other ones: gayOS, Winshit or cucklicenseBSD, mainly because they're nonfree and/or just as bad as Linux anyhow.
you cannot write correct code in C that isn't effectively just a basic b***h deterministic state machine with no dynamic allocations and knowable stack usage, period. cope all you want but it's true.
2 weeks ago
Anonymous
>incoherent screeching
When the HRT kicks in
2 weeks ago
Anonymous
What troonyOS are you posting from?
Because I wasn't aware there was an OS written in Rust...
2 weeks ago
Anonymous
I will also add that C use in things like ABS micros and other critical systems is really detached from what I'd call C, since in those environments your code is:
extremely likely to be deterministic anyhow and trivial to prove correct with any model checking.
depends on so many not-c features it's just flavored assembly.
2 weeks ago
Anonymous
you cant cure moron with procedure.
latest in date: picrel
sauce: https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=rust
have a read, lads. it really shows you what is to expect with rust as an ecosystem,and its tendency to false-positive safety.
rust is even worse than C for thickies.
thats because they believe rust takes care of your memory and lifteimes automajically bc muh borrow checker and such
and, well...
it doesnt.
>more systems to get lost in didnt fix the issue of morons being too moronic for certain jobs >how in the world could that happen?
-corporate
2 weeks ago
Anonymous
>rust takes care of your memory and lifteimes automajically bc muh borrow checker and such
that is correct
2 weeks ago
Anonymous
>you cant cure moron with procedure.
yes, you literally can. you're the kind of moron who would lose both his hands because he didn't follow the work instructions working in a forgings plant (this actually happened in my workplace recently).
you're a delusional troony who is overconfident and will get burned.
>the ultimate order of the party was to reject the evidence of your eyes and ears (or something to that effect)
thats not what the cves say, crabs.
in fact, what youre showing is schizophrenia and so you have nothing to do anywhere close anything tech or science related.
2 weeks ago
Anonymous
you don't know what you're talking about and you're moronic. stay ignorant. meanwhile I'll write software that's much more testable and closer to correctness than anything you can make, troony moron.
2 weeks ago
Anonymous
dumb pathetic moron
>ad homonems
i accept your abject and utter concession, so aptly underlined with impotent anger. how delicious.
also thanks for the yous btw
2 weeks ago
Anonymous
>muh logical fallacy
your whole argument is one. it's founded on no-true-scotsman. seethe all you want but what I said is correct and you're wrong. I've seen it firsthand and I've also seen first hand what Rust lets you do and what Rust very intentionally makes hard.
again moron, your software is basically unimportant throwaway garbage for the mentally moronic, read: (You).
2 weeks ago
Anonymous
lol. crabs arguing with mitre.
how cute.
but i wonder...
if mitre is fallacy, why do you keep using it to bash C? >schizophrenia, my old friend
2 weeks ago
Anonymous
dumb pathetic moron
2 weeks ago
Anonymous
>you cant cure moron with procedure.
yes, you literally can. you're the kind of moron who would lose both his hands because he didn't follow the work instructions working in a forgings plant (this actually happened in my workplace recently).
you're a delusional troony who is overconfident and will get burned.
>tell management that "it'll be done when it's done"
I would say it in a more polite way but I've done this many times. Asking politely is the easiest way to get what you want in most social settings.
>tell management that "it'll be done when it's done"
I don't really see how this relates to C.
I program mainly in C and C++ and I can give time estimates to management.
>Coding really should be left to 150 IQs
Then C and Unix wouldn't exist. People smart enough to properly use tools made by stupid people are smart enough to make better tools.
>C and UNIX are bad >almost everything useful is written in C >everything and the kitchen sink has a POSIX layer and UNIX-like FS hierarchy >even Microsoft is invested in WSL >even Apple crap is based on BSD under the shiny buttons
Curious.
2 weeks ago
Anonymous
and the kitchen sink has a POSIX layer and UNIX-like FS hierarchy
Because of government mandates. >>even Microsoft is invested in WSL >>even Apple crap is based on BSD under the shiny buttons
Because free labor is more profitable than good design.
2 weeks ago
Anonymous
you cant make money with a bad design tho (nta).
or we would all be using temple os
2 weeks ago
Anonymous
I think POSIX is the least-terrible thing as a mainstream OS API. But it's not without warts. File descriptor numbers aren't randomized (the equivalent to ASLR). EPIPE. Not enough atomic filesystem operations. Signal handlers. Syscall error codes are unreliable.
And a lot of the useful things are actually non-standard extensions like io_uring, procfs or reflink copies.
2 weeks ago
Anonymous
>File descriptor numbers aren't randomized (the equivalent to ASLR). EPIPE. Not enough atomic filesystem operations. Signal handlers. Syscall error codes are unreliable.
Not all operating systems have things like that. "File descriptor numbers" are a Unix thing that most systems don't use. A lot of operating systems have scoped error handlers instead of global signal handlers.
SQL injection and CSS can't affect C++. But it doesn't matter if the software could technically be written in C. They're not and they still have vulnerabilities. In fact, vulns in non C languages are more dangerous in terms of global impact.
2 weeks ago
Anonymous
>SQL injection and XSS can't affect C++.
based on what, moron? It's possible to write a C++ web service that would be vulnerable to both of these.
I've worked on a similar one that was actually vulnerable to path traversal as well.
It's more like a bike that's chained to a pole so you can only ride around in circles for your own safety. If you actually want to go anywhere you have to unchain the bike and ride it through heavy car traffic anyways. Crates are like shoving a stick through the spokes and crying when you bust your head on the pavement.
yeah, well, turns out cniles need safety wheels
>I can't write safe C, that means nobody can
Coding really should be left to 150 IQs
>that means nobody can
unironically, yes.
that's how systems are designed. you'd know this if you weren't a toddler making bing bing wahoo widgets for worthless office wagies and their moronic children.
Funny how git and Linux just work
yes, barely.
you will also note that Linux use in critical systems is basically non-existent and to this day people post meme blogs about how they defeat linux ASLR, get a use-after-free primitive in some meme feature and make everyone seethe.
reminder to turn off io_uring or any new meme garbage feature in Linux. Not even Google uses most the new shit for a reason.
>autistic HRT-induced screeching
Thought so
no argument moron-kun?
I worked on some industrial shit in the past and the Linux component was just an overglorified DBMS with some basic user controlling features.
all the hard safety features are targeted outside of Linux. In fact, many customers still prefer the pre-Linux ARM shitbox devices to this day. Using Linux is fine and all, but you're a delusional troony if you think you should trust your life to an extremely complex, non-realtime operating system with a known history of merging extremely shitty code and still have very weak security programming practices or testing methodologies.
Linux is a dog shit code base and you're moronic. Note I'm not defending any of the other ones: gayOS, Winshit or cucklicenseBSD, mainly because they're nonfree and/or just as bad as Linux anyhow.
you cannot write correct code in C that isn't effectively just a basic b***h deterministic state machine with no dynamic allocations and knowable stack usage, period. cope all you want but it's true.
>incoherent screeching
When the HRT kicks in
What troonyOS are you posting from?
Because I wasn't aware there was an OS written in Rust...
I will also add that C use in things like ABS micros and other critical systems is really detached from what I'd call C, since in those environments your code is:
extremely likely to be deterministic anyhow and trivial to prove correct with any model checking.
depends on so many not-c features it's just flavored assembly.
you cant cure moron with procedure.
latest in date: picrel
sauce: https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=rust
have a read, lads. it really shows you what is to expect with rust as an ecosystem,and its tendency to false-positive safety.
rust is even worse than C for thickies.
thats because they believe rust takes care of your memory and lifteimes automajically bc muh borrow checker and such
and, well...
it doesnt.
>more systems to get lost in didnt fix the issue of morons being too moronic for certain jobs
>how in the world could that happen?
-corporate
>rust takes care of your memory and lifteimes automajically bc muh borrow checker and such
that is correct
>the ultimate order of the party was to reject the evidence of your eyes and ears (or something to that effect)
thats not what the cves say, crabs.
in fact, what youre showing is schizophrenia and so you have nothing to do anywhere close anything tech or science related.
you don't know what you're talking about and you're moronic. stay ignorant. meanwhile I'll write software that's much more testable and closer to correctness than anything you can make, troony moron.
>ad homonems
i accept your abject and utter concession, so aptly underlined with impotent anger. how delicious.
also thanks for the yous btw
>muh logical fallacy
your whole argument is one. it's founded on no-true-scotsman. seethe all you want but what I said is correct and you're wrong. I've seen it firsthand and I've also seen first hand what Rust lets you do and what Rust very intentionally makes hard.
again moron, your software is basically unimportant throwaway garbage for the mentally moronic, read: (You).
lol. crabs arguing with mitre.
how cute.
but i wonder...
if mitre is fallacy, why do you keep using it to bash C?
>schizophrenia, my old friend
dumb pathetic moron
>you cant cure moron with procedure.
yes, you literally can. you're the kind of moron who would lose both his hands because he didn't follow the work instructions working in a forgings plant (this actually happened in my workplace recently).
you're a delusional troony who is overconfident and will get burned.
https://github.com/search?q=repo%3Agit%2Fgit+%22use+after+free%22&type=commits
>Funny how git and Linux just w- ACK!
https://lore.kernel.org/linux-cve-announce/
tell management that "it'll be done when it's done"
see how that works out for you if you refuse to rush and cut corners
If it's worth doing, it's worth doing right
>tell management that "it'll be done when it's done"
I would say it in a more polite way but I've done this many times. Asking politely is the easiest way to get what you want in most social settings.
>tell management that "it'll be done when it's done"
I don't really see how this relates to C.
I program mainly in C and C++ and I can give time estimates to management.
>Coding really should be left to 150 IQs
Then C and Unix wouldn't exist. People smart enough to properly use tools made by stupid people are smart enough to make better tools.
>C and UNIX are bad
>almost everything useful is written in C
>everything and the kitchen sink has a POSIX layer and UNIX-like FS hierarchy
>even Microsoft is invested in WSL
>even Apple crap is based on BSD under the shiny buttons
Curious.
and the kitchen sink has a POSIX layer and UNIX-like FS hierarchy
Because of government mandates.
>>even Microsoft is invested in WSL
>>even Apple crap is based on BSD under the shiny buttons
Because free labor is more profitable than good design.
you cant make money with a bad design tho (nta).
or we would all be using temple os
I think POSIX is the least-terrible thing as a mainstream OS API. But it's not without warts. File descriptor numbers aren't randomized (the equivalent to ASLR). EPIPE. Not enough atomic filesystem operations. Signal handlers. Syscall error codes are unreliable.
And a lot of the useful things are actually non-standard extensions like io_uring, procfs or reflink copies.
>File descriptor numbers aren't randomized (the equivalent to ASLR). EPIPE. Not enough atomic filesystem operations. Signal handlers. Syscall error codes are unreliable.
Not all operating systems have things like that. "File descriptor numbers" are a Unix thing that most systems don't use. A lot of operating systems have scoped error handlers instead of global signal handlers.
unfortunately/fortunately that excludes (You)
STFU troony.
Most of these categories disproportionately affect languages other than C/C++ like PHP, Python, JavaScript and SQL.
cope
Because most people don't want to write complex networked software in C and C++.
SQL injection and CSS can't affect C++. But it doesn't matter if the software could technically be written in C. They're not and they still have vulnerabilities. In fact, vulns in non C languages are more dangerous in terms of global impact.
>SQL injection and XSS can't affect C++.
based on what, moron? It's possible to write a C++ web service that would be vulnerable to both of these.
I've worked on a similar one that was actually vulnerable to path traversal as well.
It's more like a bike that's chained to a pole so you can only ride around in circles for your own safety. If you actually want to go anywhere you have to unchain the bike and ride it through heavy car traffic anyways. Crates are like shoving a stick through the spokes and crying when you bust your head on the pavement.
and that's a GOOD thing