Apple Files Patent for "Tamper-Resistant Code"
freaktheclown writes "The US Patent and Trademark Office has revealed that Apple has filed patent no. 20050246554 for a "system and method for creating tamper-resistant code." The system is presumably for use in Apple's Intel version of its Tiger operating system."
Nothing beats the smell of a homebrewed mac in the morning :)
Online backup with Mozy, sounds like Ozzie, but more!
It's called "tamper-resistant" because the Titanic was unsinkable.
"Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
I do believe HAL 9000's tamper resistant code kicked into high gear around hour 2 of 2001.
"I'm sorry Dave, I can't let you do that"
They are patenting Perl?
I for one welcome our new tamper-resistant overlords.
Get your Unix fortune now!
it's candle proof? it can't be narrowed?
No worries mate, it worked out pretty good for OS/2 Warp.
The more you know, the less you understand.
I'll gladly translate into multiple dialects for you.
Marketing language:
"20. A method comprosing: receiving a system call, wherein the system call is in synergy with other components of a system, wherein the sum of the system is leveraged to meet market demands in a new and fundamentally influential way, wherein a paradigm-shift results from the impact of the novel processes and inherently forward-looking business model that thereby ensues."
Money language:
"20. A method comprising: we program our computer to do something, someone else somewhere on earth programs their computer to do something that turns out to be similar; we determine that they have a computer doing something that only we are allowed to do; we sue; we make money."
Tinfoil-hat language:
"20. A method comprising: receiving a system call, wherein the system call is formatted to include all personal information on the computer, wherein this information is then encrypted and sent off to corporate HQ servers in order to be analyzed and thereafter used against the user of the originating personal computer sytem."
(very) Plain english:
"20. A method comprising: stuff happens."
Plain english:
"20. A method comprising: A translation layer between different operating system abstraction levels. When a running program (which may have been translated from a stored version of the program) makes a system call to the operating system, this methodology will handle that system call in such a way as to be "tamper resistant." For instance, it will only allow operations determined to be acceptable."
I'll just set that on the wall next to the unpickable lock, the unstealable car, and the unhackable DRM.
~X~
~X~
Also, Slashdot seeks new software to spell-check all posts, especially those that misspell words in the topic title, which appears in the title bar while viewing the page.
That's not a good analogy. If flame-resistant blankets were like tamper-resistant code, once fire managed to burn the blanket it would then post all over the internet describing how it succeeded, resulting in increasingly efficient burning of said blankets.
I recently had a friend ask me for help in debugging a PHP extension for some CMS... Ah, Google to the rescue; it was SEF Advance, a Joomla extension that did... something, I never really bothered to find out. Anyway, issue was that the guy was trying to debug the script locally (maybe to add something) and it was saying that it "was only licensed to x and y domains", where x and y were the production servers. The code itself was a bunch of open source config variables, then a statement as follows:
:^D)
eval(gzinflate(base64_decode('7T39Vxs5k...')));
The parameter went on for ages. When I changed the eval to echo, I got another block of the same, only the data was different. Apparently the guy had just gzipped his code over and over (five times to be exact) and used that as "encryption" so nobody would be able to modify it. I got around it in around five minutes, and sure enough, the domains were simply an array in the decrypted (inflated?) code.
The point is, according to the parent, it looks like Apple is patenting object code encryption, which has been done many, many times before in many different ways. I'm sure that the rest of the patent indicates something "unique" (and I put unique in quotes because there's no way to know it hasn't been done before somewhere) but in the end it's just diminishing possible future innovations by a little bit, like all software patents.
(Does this mean I'm liable under the DMCA?
It's better to vote for what you want and not get it than to vote for what you don't want and get it.
- E. Debs