Slides for my "Coverage-guided USB Fuzzing with Syzkaller" talk @offensive_conhttps://docs.google.com/presentation/d/1z-giB9kom17Lk21YEjmceiNUVYeI6yIaG5_gZ3vKC-M/edit?usp=drivesdk…
I didn't make the deny_new_usb feature. I developed the Android integration for it including integration into Keyguard for automatically enabling it when the screen is locked. It existed as a kernel feature for many years prior but hadn't been properly integrated as intended.
There's an upstream kernel feature (https://kernel.org/doc/Documentation/usb/authorization.txt…) which I worked on integrating as a more sophisticated feature where users can confirm the device types match their expectation. Unfortunately, it was only a prototype and wasn't ever ported to later releases of Android.
I picked up the patch from the Linux Hardened tree you were maintaining a while back (thanks!), so the patch I use has your name as the git author. What was the original provenance? PaX/grsec?
The commit states the origin (grsecurity). Being the author of a commit doesn't imply being the original author of the code. The origin of the patch wasn't published as a Git repository and even if it was there wouldn't necessarily be a usable commit to directly extract that way.