Originally posted by Slartifartblast
View Post
Do you have a problem with hoping that a large piece of filesystem driver code gets a proper treatment coming from the outside?
But to answer your question. Not a security audit, no.
But I've actually read the code for OHCI core, UHCI, EHCI and XHCI on more than one occasion at different points in time.
Sure. Not all the port platform drivers, but then again, I haven't used most of them.
I've only done full security audit of code outside the kernel.
I've done some basic security auditing of added code to the kernel though.
But then again, being an embedded Linux developer for 20 years+,
having built all minor revisions of the kernel since 2.0.3x-something (I think).
Done mips, hp-ux, sparc, blackfin, sh, arm, x86, xtensa, cris, powerpc archs and probably a few more boards and ports.
I did my master thesis on free CPU architectures 18 years ago.
But that probably does not count for shit right?
Phoronix members going zero to full retarded fangs out in the forum are probably the only ones on the planet with a clue...
Leave a comment: