Linux can lead in reviving competition
Operating Systems can benefit from encryption even without encrypted computing.
Encrypted computing has been described. Hollywood is aware that bootlegging can be minimized by encrypting separately for every digital projector.
This could work for MP3's as well. CD rippers would have to be modified to accept a user account encryption key with a distinct rip for every instance of an installed OS. Legacy CD's themselves would not be affected. Later, each CD might have it's own decryption key, but that leads to users needing extensive key-rings, with a unique key for any of 50 or more CD's. MP3's purchased online could be encrypted by the vendor.
We also theorize that computer OS's can be made harder to steal, if each copy of the OS has it's own unique key. Microsoft already has an authentication key, but it does not encrypt the distributed copy with it.
Business solves a problem when it encrypts separately for every user, but the problem of bootlegging is only addressed with real force, if the key is necessary to use/run the application.
Theorize an OS with an encryption key, that encrypts even the applications with the user password. When you purchase it, you purchase it by providing the encryption key that you intend to use, and it comes encrypted. The OS is written so that the user password is employed every time an application is launched, to actually decrypt the object code.
The applications themselves would run unencrypted in RAM.
The password need not be re-entered at every launch of a program, but rather the user account could accept the password at login, and the login password could be the same as the user account.
Under this model, an unencrypted copy would be hard to use or distribute bootleg. The bootlegger would be tasked, first with decrypting, then with re-encrypting each bootleg copy with the key of the user that he was stealing it for.
It would have the side effect of making two users on the same PC require a separate instance of the program object code, to run on the same machine, because they each have a unique user password. This could be accomplished with the purchase of two licenses, or compiling some source code twice, once for each user account.
This works for commercial applications - how does it affect a student or an amateur programmer?
His compiler would be responsible for encrypting the app in such a way that it required the user account password to run. Then, if he chose to distribute it, he would be responsible for encrypting it separately for each user he favored with a copy.
Compiling is different than executing, so this might be a doable solution, that would be worth researching the details.
It would be to the advantage of the programmer, not to save ANY unencrypted copies. Source files would be encrypted as text, and the compiler would encrypt for the user account, when compiling. Text files would be unencrypted in RAM, and transferred over email, just as we currently do.
Compiled instances then would be saved by the compiler ready to use the account password to run. To compile for a different user, the compiler would have to ask for the password of the third party. Would it be secure, to share this information?
Since decryption is
required to launch, an unencrypted copy would be distributable, but only
to individuals who invested in compilers of their own. This does not
affect the distribution of compilers themselves. If they come as part of
the OS, they match the user account, and if you download/purchase them
online, you provide your key as a credential.
To spy on a computer, could you boot an OS instance with a stolen credential, and come in over Internet Protocol, stealing data as if it was the same machine? It certainly would make mass surveillance inconvenient.
When I encrypt my Linux partition, the files are stored encrypted. When I mount the partition, I expect that a third party coming in over Internet Protocol can download the file unencrypted. Currently, a mounted encrypted container is similar to an unencrypted container. I believe that there is block encryption that can accommodate random access. I have seen it on Trucrypt.
Finally, this would leave an inevitable weak link: An unencrypted copy of the OS would be valuable to steal. The thief could then encrypt it for as many friends as he liked. However, this would be mitigated by current authentication protocols.
If the Linux community solved this problem before Microsoft (or Apple, or Google Android,) they could monetize distribution, and solve a major problem for American capitalism. It's a lot to ask, but it might be commercially worth it!
Comments
Post a Comment