One of the lamer suggestions I heard from an instructor at some unmentionable educational institution some years back was that you could boost the number of graduates simply by lowering the standards. At the time, I thought the person who made this foolish statement probably could use a new job, perhaps one at a local fast food restaurant.
IÃ¢â‚¬â„¢ll explain what IÃ¢â‚¬â„¢m getting at shortly.
To begin with, as Apple patches more and more security leaks in Mac OS X, you have to wonder when or if any of them will be exploited. I mean, if you read the nasty details of a typical problem, you canÃ¢â‚¬â„¢t help but feel just a little less secure.
Take the most recent update released this month. Among over two dozen fixes was one that addressed this deficiency: Ã¢â‚¬Å“A memory corruption vulnerability exists in fsck. It is possible to cause fsck to be run automatically on a disk image when it is opened. By enticing a user to open a maliciously-crafted disk image, or to run fsck on any maliciously-crafted UFS filesystem, an attacker could trigger the issue which may lead to an unexpected application termination or arbitrary code execution.Ã¢â‚¬Â
All right, weÃ¢â‚¬â„¢ve all got to be on the lookout for a Ã¢â‚¬Å“maliciously-crafted UFS filesystemÃ¢â‚¬Â or a Ã¢â‚¬Å“maliciously-crafted disk image.Ã¢â‚¬Â Heaven knows whatÃ¢â‚¬â„¢ll happen.
On the other hand, has there ever, anywhere, been such an attempt other than in a laboratory?
Story continued in this week’s Tech Night Owl Newsletter.
| Print This Article