-
Notifications
You must be signed in to change notification settings - Fork 0
Asset DRM and/or protection. #79
Copy link
Copy link
Open
Labels
help wantedExtra attention is neededExtra attention is neededom-clientIssues relating to the OpenMinerva client.Issues relating to the OpenMinerva client.om-serverIssues regarding the headless server.Issues regarding the headless server.questionFurther information is requestedFurther information is requested
Description
Metadata
Metadata
Assignees
Labels
help wantedExtra attention is neededExtra attention is neededom-clientIssues relating to the OpenMinerva client.Issues relating to the OpenMinerva client.om-serverIssues regarding the headless server.Issues regarding the headless server.questionFurther information is requestedFurther information is requested
This is going to be a topic that I am going to need help with researching and deciding on the proper solution(s). I would like to create some form of asset protection and/or some mechanism to help prevent asset theft.
Before contributing to this discussion I just want you to know that I know that there is not a way to stop asset theft. I know that at some point the file(s) must be decrypted and be rendered. Replying to this thread with "Once it hits the GPU it can be stolen" or other such comments are unhelpful and unproductive. The aim is to make it harder for assets to be ripped and stolen. Another goal is to keep uploads inline with licenses provided by models or assets.
Something that I think I could start with this problem is cache encryption. When sending files to other clients, you as the uploader encrypt the file and send the encryption key with the file. The end result is that the file is locally encrypted, and the client will be able to request the encryption key from clients on-demand.
I would like to know if there are any more ideas on this topic, or if there are issues with this idea that would make this unrealistic or insufficient.