Printer of Doom
via Corey Nachreiner, CISSP and Director of Security Strategy for WatchGuard Technologies.
via Corey Nachreiner, CISSP and Director of Security Strategy for WatchGuard Technologies.
Evidently, crank developers are now targeting Cupertino, California based Apple, Inc.'s (NasdaqGS: AAPL) decision to out the utilization of location data by apps resident on iOS devices, even when an app is not running...
The company's own apps require authorization as well; perhaps the coming singularity is slowing down, just a tad, mind you... Certainly a contrarian view.
via the inimitable Gina Smith at ANewDomain
Evidently, seventeen thousand Apple Inc. (NasdaqGS: AAPL) MAC OS X machines (worldwide) have been corralled into a nefarious botnet. Discovered by a relative unknown in the burgeoning Russian anti-virus industry (nope, it wasn't Kapersky) this bot is probably the prettiest ever, eh Comrade? One bit of good news, Apple has released a new malware definitions update as of 11:00 AM yesterday.
Much ado about something, nearly a quarter century in the offing, and further evidence to support our Theory of Cruft, or the Things that are Left Over, and Getting in the Way...
Outstanding screed, penned by Nicholas White, writing at The Kernel, details the apparent Gentrification of Cybercrime. Who'd A Thought... An electronic Thomas Crown, eh wot?
{with apologies to the Blandings...}
Ladies and Gentlemen, Girls and Boys, here's why Apple Inc. (NasdaqGS: AAPL) iOS 8.x driven devices are marginally better for privacy concerns: Rotating (Programmatic MAC Spoofing) Media Access Control addresses. Today's MustRead; whilst, another view of tracking iOS devices has surfaced.
Newly discovered BASH vulnerability finds Apple Inc.'s (NasdaqGS: AAPL) MAC OS X operating system with it's shell environment cracked; of course, this pernicious bug also finds its way into most Linux and/or other Unix-like and UNIX systems. Interestingly, there are workarounds and patches available for the version of BASH resident on your OS X systems. If you look hard enough, there is a workaround in the StackExchange article (linked to above).
Cogitate thrice upon updating newly released software with newly released patches to fix newly discovered bugs, as evidence of cruft...