Targeted Fuzzing Is Improving Linux Security, Linus Torvalds Says (iu.edu)
On the sidelines of announcing the fifth release candidate for the Linux kernel version 4.14, Linus Torvalds said fuzzing, which involves stress testing a system by generating random code to induce errors, is helping the community find and fix a range of security vulnerabilities. He wrote: The other thing perhaps worth mentioning is how much random fuzzing people are doing, and it's finding things. We've always done fuzzing (who remembers the old "crashme" program that just generated random code and jumped to it? We used to do that quite actively very early on), but people have been doing some nice targeted fuzzing of driver subsystems etc, and there's been various fixes (not just this last week either) coming out of those efforts. Very nice to see.
This sound like an area where AI could be really helpful.
Since darwin is based on linux kernnel, the number of linux patches has been on the rise with strong backing from corporate apple
..I thought "Targeted Fuzzing" was about growing pubic hair in designated patches.
drop some shrooms and mdma and PLUR your way to random code those security holes out while listening to 4 on the floor Techno.
by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
Structured fuzzing is also very effective at finding compiler bugs.
BUT IT'S WRONG!
I use the crashme program to generate random code. Then I run it through Google translate and self publish on Amazon. Not a bad way to make a living.
"A person is smart. People are dumb, panicky dangerous animals and you know it." - K
If you really want to understand Linus Torvalds and Linux, read "Just for Fun: The Story of an Accidental Revolutionary".
I see a lot of asks to fuzz test ICMP and TCP in hopes of finding application-layer issues in various high-level protocols. I see this as a giant waste of time. Am I wrong?
Only 381 Linux Kernel CVE's so far this year. To date, that is 164 more than last year, and by far the greatest number found. 166 code executions found this year, which is more than 8 times all other years COMBINED.
Granted, most of that is on the Android side of things. But at this point, there is more than 1 vulnerability in the linux Kernel found every day, and a code execution found every other day.
Source:
http://www.cvedetails.com/product/47/Linux-Linux-Kernel.html?vendor_id=33
As maintainer of a small open source library and program I have benefitted immensely from the efforts of a small number of volunteers running fuzzing programs and using Address Sanitizer to locate bugs in the code I maintain. These volunteers have found bugs and reported them and provided testcases useful for regression testing. I am profoundly grateful to these folks.
The hail-mary of testing when you just can't find that last &#@$! bug.
i dunno, but having two different "alphabets" in same unicode space:
1) A "A" or ">" etc. that has a (fictional) unicode code of say 456 and 223.
2) A "A" or ">" etc. that has a (fictional) unicode code of 2076 and 4432. All >1024.
For Input's to compileD programs only Unicode code larger-then 1024 are filtered and allowed. ...?
For running programs or for programming only Unicode code smaller then 1024 is allowed
Thus all Input's larger-then 1024 by a "program user" cannot alter the code. :]
However the program path can still be shitty
Back in the 70s when there were various mini computer manufacturers each with their own architecture. I worked for one of those, and we tested our code. I don't think anybody did deliberate 'fuzzing' (though I do believe a concept kinda like that was talked about.) But some pretty hairy bugs were found by accident. People making typos when trying to enter legitimate commands, that kind of thing.
In theory, theory and practice are the same; in practice they're different. (Yogi Berra & A. Einstein)
A good use for systemd