Two comments;
Bluetooth. Linux distributions generally ship with bluetooth support. And even when you remove the drivers or tools to manipulate bluetooth, often various frameworks will retain vestigal folders, libraries on occasion, so on. They are not in use and have no operational impact probably but they are there due to anything from sloppy programming to license weirdness.
Second comment; never forget that with any contemporary linux distro, 80% of the code is just sloppy workarounds to mitigate other peoples errors that have become architectural canon. So often, things appear not to make sense simply because we are exposed to compromises, not solutions.
Bonus third comment:
http://www.chromium.org/chromium-os/...he-source-code
When you see a message like "TMP not OWNED", consider strongly doing a recursive grep through source code looking for that error. The effort may or may not be useful or productive but its certainly immsersive and the answer is literally always in there.
I just woke up at midnight from a 3 hour nap and I have to pick my father up at the airport in like 23 hours so Im a bit of a mess. I certainly consider it possible that you have a legitimately corrupted Chromebook but Occams Razor says you misinterpreted a benign error and flipped the wrong bit and made it worse, of course. Which is something computer people are rather known for.
In other news I have to root one final server in my lab and because its got libssp installed, I believe I have to smash a vulnerable stack on an application and perform something called a return-to-libc attack by pointing my return address at a pre-established libc function. Which is fucking insane to begin with. And doubly so because I cannot find a binary vulnerable to a buffer exploit on it.
Motherless leapfrogging Christ.
Linear Mode
