4 ms·
Separating code from knowledge was part of the fun of the decss debacle. "That's not a haiku; that's an illegal perl script!"
by tedunangst 10y ago
Separating code from knowledge was part of the fun of the decss debacle. "That's not a haiku; that's an illegal perl script!"
- AnthonyMouse 10y agoAnd fundamentally it's the knowledge that matters. Programmers are "expensive" but not that expensive. Give any decent off-the-shelf code monkey the specifics of a vulnerability and he can give you exploit code. Which means restricting the exploit code is quite useless. But restricting the knowledge itself doesn't work because the same knowledge is necessary to mitigate the vulnerability and to test that the mitigation is effective.
- makomk 10y agoThese days, exploiting vulnerabilities in most interesting code actually seems to be quite fiddly thanks to all the mitigation techniques and requires a bunch of specialist knowledge and tools that isn't exactly trivial to come by. The knowledge is already restricted, just for commercial rather than legal reasons.
- AnthonyMouse 10y agoWhich is still knowledge. If you have the information you can make the tools. I mean obviously in reality the line between "information" and "software" is non-existent because software is just a type of information, but if you insist on trying to draw a line anyway then it still fails because it's still possible to convey everything of significance using natural language, and the skillset required to convert plain language instructions into software is not rare enough to be prohibitive.
- pixl97 10y ago>thanks to all the mitigation techniques and requires a bunch of specialist knowledge and tools that isn't exactly trivial to come by Eh, specialist knowledge yes. Restricted, no. Getting documents on how chips and software has always been somewhat restricted, just be a linux person and try to get documentation from Broadcom on how their wifi/lan chips work, for example.
- hackuser 10y agoI don't recall seeing that spirit and creativity in a long time. Or am I just getting old and cranky? The battle for end-user control seems surrendered, at least by all but a few.