its a shame about every 1 havin the same publisher key cos it means that every1 can open every1 elses EXEs
but wasnt the source for the publisher key included in the main source distribution? im sure it was and if so couldnt we use it to compile our own unique publisher keys? I dont see anything wrong with doin this.
any1 here got any tips on doin this?
At the download here is a Key at the name of the Blender Foundation. This is a free Key, which allows all Blender Publisher features, including writing locked content.
A dot-exe doesn't have to be locked, that's an option you can choose for.
By publishing this Key, it means that 'locking' doesn't really lock the file, since anyone with a Foundation key can read it.
The people who have bought an official Key in the past, can still lock their content.
With an open source Blender, we have to define if anyone still wants the locking feature. I would propose to remove it from the main source tree, and make it a seperate utility which artists can use if they like. This proprietary locking feature doesn't really match an open project imho...
you cannot open a exe, unless you want to look at the binary
Life is what happens to you when you're busy making other plans.
- John Lennon
Seems Blender is just ignoring the player in front(?) of an EXE.
But to say again: You CAN'T open an file or EXE which was locked with a *different* key!
Yeah I know, but since its all open source now anyway whats the harm in releasing the details of how to generate your own key?