List Recv
3/31/2006 3:54:00 AM
I still don't understand. Who are you trying to protect - a user from
running a malicous (or tampered with) ruby script? If so, as I said,
this is no different than protecting a user from running a trojan
compiled file - people either trust the author (and hopefully use code
signing), or run the code in a sandbox.
In terms of ensuring that only admin's can install the ruby
executable/interpreter - this is currently impossible, and likely will
remain so. Even if you mark your exe/interpreter to require admin
privs to install, what's to stop anyone else from creating their own
exe/interpreter without that restriction? It's essentially the old
copy protection / DRM issue, which all experts agree can always be
defeated (at least short of a hardware implementation).