-
1st coding period of GSoC'19 is over and I have made some progress in improving support for
@netbsd in the#syzkaller kernel fuzzer. http://blog.netbsd.org/tnf/entry/enhancing_syzkaller_support_for_netbsd … -
Qualcomm Mobile Security Summit 2017 presentations https://goo.gl/TzyhNH Incl mine on
#syzkaller. The leakage one was fun. -
It's fascinating to see changes like this due to your work: whole class of inbound IPv6 packets is now unconditionally dropped by all Linux machines out there right in ip6_rcv_core() because... nothing good will happen otherwise: https://www.mail-archive.com/netdev@vger.kernel.org/msg315880.html …
#syzkaller -
Had a great time working with the
@netbsd foundation as a part of GSoC'19. I worked on enchancing support for the#syzkaller kernel fuzzer. https://blog.netbsd.org/tnf/entry/enchancing_syzkaller_support_for_netbsd1 …https://twitter.com/teambi0s/status/1172165680340168704 … -
I wrote a post: "Case study: Searching for a vulnerability pattern in the Linux kernel". It's a funny story about
#syzkaller,@Semmle@LGTM, Coccinelle and a "public 0day".https://a13xp0p0v.github.io/2019/08/10/cfu.html … -
.
@Tr3x__ of our team delivered a talk on#day3 in the fuzzing track of@nullcon where he talked about Coverage Guided Fuzzing,#syzkaller, and results the@netbsd community got after porting syzkaller to NetBSD recently :)pic.twitter.com/20b4YcV1R5
-
The value of attending conferences like
@KernelRecipes expressed in a single pr: https://github.com/google/syzkaller/pull/1434 … Proper#syzkaller fuzzing support for#pidfd codepaths. Spent a good hour with@dvyukov getting things in order. :) Now off to enjoy my last hours without bug reports. :) -
Got accepted into
#GSoC 19. Had such an awesome time last year with@netbsd that I decided to go for it again. I will be working on better integration of#syzkaller kernel fuzzer with the NetBSD kernel. Looking forward to another fabulous summer with this amazing organization. -
The incredible
@yoavalon and@netanelbensimon presenting at@bluehatil on modifying#syzkaller to find Windows Kernel vulnerabilities pic.twitter.com/nPblrHGHRX
-
@dvyukov let's see if I got the new set_tid feature@adrian__reber sent for v5.5 into#syzkaller correctly: https://github.com/google/syzkaller/pull/1519 …
-
Minor out-of-bounds read in smk_set_cipso() root$ echo "test 1" > /sys/fs/smackfs/cipso2 https://lkml.org/lkml/2019/11/20/633 …
#syzkaller#LinuxPrikaži ovu nit -
Smack LSM module descriptions for
#syzkaller https://github.com/google/syzkaller/pull/1513 …Prikaži ovu nit -
I was running a
#syzkaller instance for some time. Bad luck - it didn't find anything and sometimes was loosing connection to VMs. The alert from Fedora DE about QEMU was a clue. Then I used@mozilla rr for debugging QEMU and rr hanged :) I'll fix it. Actually it's a good luck. -
Peeps are working on porting
#syzkaller to#FreeBSD. They already found issues: https://lists.freebsd.org/pipermail/freebsd-hackers/2017-October/051530.html …#infosec -
Quick notes about syzkaller source code: https://github.com/hardenedlinux/Debian-GNU-Linux-Profiles/blob/master/docs/harbian_qa/fuzz_testing/syz_analysis.md …
#syzkaller#qa#fuzzer -
Anton Lindqvist (anton@) "Add kcov(4), a kernel code coverage tracing driver. It's used in conjunction with the
#syzkaller kernel fuzzer. So far, 8 distinct panics have been found and fixed. This effort will continue."#OpenBSD https://marc.info/?l=openbsd-cvs&m=153467896308034&w=2 … -
Didn't receive any PRs for
#virtiofs support in#syzkaller. So waiting for more#linux KVM guest escapes and priv escalations. +more work for stable and all downstream maintainers to put down fires later. Stuff moar unfuzzed code into kernel! My job security goes through the roofhttps://twitter.com/kernellogger/status/1190610980809527296 …
-
The syscall descriptions from the
#syzkaller project might be useful here? https://github.com/google/syzkaller/tree/master/sys/linux … -
Oh, that's nice:
#syzkaller supports@openbsd https://syzkaller.appspot.com/?fixed=openbsd
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.