|
|
|
| Authored by: Anonymous on Sunday, June 10 2012 @ 12:15 PM EDT |
It's pretty well shown that there's a *long* distance between
"It happened"
and
"She intended it to happen".
Most of the time, the distinction is fairly easy. Most developers don't
re-write their boot disks very often, since they don't re-write their operating
system very often. Most users aren't even developers. I don't see making it
unscriptable without some explicit action on the owner's part (like specifically
enabling a certain script to do it, outside the script itself) as a problem. If
you want to play, then go ahead...at some point, I have to assume that you are
smart enough to realise that the move is insecure, and you will need to take
other steps if you want assurance that the result is also secure.
And modifying the OS without notice is how most viruses propagate. So forcing
intentionality with *reasonable* certainty isn't all that difficult. I vote the
best method is to have you write out a new boot CD-R. One paranoid user on this
forum already does that; it's an excellent trick.
I've also noticed that, for basic programming and fooling around, I'm using
remarkably old systems -- a 1995 compiler, various 2003 office programs from
Micro$loth, including XP, CodeWright, and an emulator I run under Windows 98.
The functionality has been remarkably stable, except for the tablet/phone
market. So your boot disk should also be stable by default.
[ Reply to This | Parent | # ]
|
|
|
|
|
