winscape 2273

Thats still not really helping. It does prevent people from easily writing software for the OS, but it does exactly nothing to prevent bugs in the compiler or emulator or whatever from trashing things.

So if I'm a developer for this signed-binary-only OS, and I go pony up my license fee to get a key the OS will accept, how is that going to make my code in the app safer? Do I submit my entire program to the OS vendor for code review? Who decides if the crash is due to my software or the OS?

If I'm a virus-malware-adware writer, I'll also be the first in line to get a signed binary key- after all the OS is now promising all signed binaries will be safe- what better way is there to increase the liklihood of people running my software?

Bounds checking is helpful- but the OS can't enforce it and if the OS allows products to run as buttembly language, the OS vendor has no control in general- the only thing the OS can do at that point is enable hardware controls to prevent wild buttembly from trashing the joint.

If the OS vendor forces everybody to run via vm or only use vendor supplied compilers, then they are welcome to their fate. This is the 21st century.

Gregm

winscape 2274
Think of it this way: You can write a compiler that targets the virtualized machine that is presented by the officially blessed compiler. A byte-code style VM and a VM...

List | Previous | Next

winscape 2274

Alt Folklore Computers from Newsgroups

The #1 Usenet Provider on the Internet

winscape 2272

PLEX86 x86- Virtual Machine (VM) Program


	CVS \| Mailing List \| Download \| Newsgroups

		winscape 2273 Thats still not really helping. It does prevent people from easily writing software for the OS, but it does exactly nothing to prevent bugs in the compiler or emulator or whatever from trashing things. So if I'm a developer for this signed-binary-only OS, and I go pony up my license fee to get a key the OS will accept, how is that going to make my code in the app safer? Do I submit my entire program to the OS vendor for code review? Who decides if the crash is due to my software or the OS? If I'm a virus-malware-adware writer, I'll also be the first in line to get a signed binary key- after all the OS is now promising all signed binaries will be safe- what better way is there to increase the liklihood of people running my software? Bounds checking is helpful- but the OS can't enforce it and if the OS allows products to run as buttembly language, the OS vendor has no control in general- the only thing the OS can do at that point is enable hardware controls to prevent wild buttembly from trashing the joint. If the OS vendor forces everybody to run via vm or only use vendor supplied compilers, then they are welcome to their fate. This is the 21st century. Gregm winscape 2274 Think of it this way: You can write a compiler that targets the virtualized machine that is presented by the officially blessed compiler. A byte-code style VM and a VM... List \| Previous \| Next



		winscape 2274 Alt Folklore Computers from Newsgroups The #1 Usenet Provider on the Internet winscape 2272