>>1065712
How it works, on windows or wherever, is this: ban the user from installing new software. Create a setuid program that will install software for them. But, this program first creates a new account, and installs it for that account. Instead of running programs directly, the user asks a setuid program to run them, which will first su to the relevant account, then run them as that account. If the user wants to change their homepage, or install software, or whatever, great, they can, because they are the user. If a malicious program (or any program) wants to do these things, they are banned, because their account doesn't have permissions.
>Is that private key truly inaccessible to malicious software?
The only way to make a file inaccessible to a program is to give the program one user, the file another user, and then set the modifiers to 0700 or equivalent.
>Is windows SOL?
All of this is possible on windows. I can give you no advice on how to accomplish it there beyond "install cygwin"