Maybe it could be:
The mods stored on the server and downloaded to LFS could be in an encrypted form that LFS game can read but LFS editor cannot read.
Then the only legitimate way to load things into your editor is by downloading the mod manually in editor form (not encrypted) via legitimate means, e.g. from mod's page when it allows derivatives, or direct from the author.
Problems with this:
1) All the mods currently on the server are in editor form and not ready to be downloaded in the proposed format. So a big switchover operation might be needed.
2) As mentioned before, this type of encryption, that anyone's S3 license can decrypt, can be easily cracked. Someone would release a decryption tool for encrypted mods, to convert game-ready mods into editor mods.
I don't know if this low level of security would be enough. It's not something I'll be doing in the near future though as you know what I am still working on.
The mods stored on the server and downloaded to LFS could be in an encrypted form that LFS game can read but LFS editor cannot read.
Then the only legitimate way to load things into your editor is by downloading the mod manually in editor form (not encrypted) via legitimate means, e.g. from mod's page when it allows derivatives, or direct from the author.
Problems with this:
1) All the mods currently on the server are in editor form and not ready to be downloaded in the proposed format. So a big switchover operation might be needed.
2) As mentioned before, this type of encryption, that anyone's S3 license can decrypt, can be easily cracked. Someone would release a decryption tool for encrypted mods, to convert game-ready mods into editor mods.
I don't know if this low level of security would be enough. It's not something I'll be doing in the near future though as you know what I am still working on.
I guess I'll have to go on thinking over time, as it appears the simple function is too controversial without other security measures, but those security measures are a much more complicated subject.
Maybe it's more like, the simple function should be in there, as a simple function and without its own security measures, but the protected model itself should be prevented from loading into the editor by unauthorised people.
But that is a whole new level of complication and I don't have any time to start trying to figure that out.
I also know in advance that is the least satisfying type of work, if I ever do it, I would have to work for many hours or days implementing things into the editor, the web server, the game, and all the while knowing that hackers will easily flip the switch, undo the encryption, etc. Setting out on a task that you know for certain will fail is never very enticing.
Maybe it's more like, the simple function should be in there, as a simple function and without its own security measures, but the protected model itself should be prevented from loading into the editor by unauthorised people.
But that is a whole new level of complication and I don't have any time to start trying to figure that out.
I also know in advance that is the least satisfying type of work, if I ever do it, I would have to work for many hours or days implementing things into the editor, the web server, the game, and all the while knowing that hackers will easily flip the switch, undo the encryption, etc. Setting out on a task that you know for certain will fail is never very enticing.
I am still working on graphics code (mainly optimisations at the moment) and need to get onto the tyre physics code and then the packet encryption. Eric still has more tracks to update. So it's still quite some time yet.
For a while, licenses were not available at BRCruse but now they are again, which can be useful as local payment methods are available for Brazilian people.
http://lfsbrasil.com/loja/en/
As stated many times recently, I am interested in making it harder for crackers to crack LFS. But there isn't really much point releasing the same current version with new crack protection, as the old one is still around. So crackers could say:
"Ah, I can have this version or that version of Live for Speed, which are exactly the same except one is easier to crack and one is harder... hmm, hmm, oh what a dilemma, hmm... what a difficult decision, hmm... what will I do?"
I think you get my point. What we need is a new and updated LFS that people do want to have, that also comes with better crack protection. Better not give up all actual development right now in order to work on crack protection. Eric will be able to use the new graphical tools that I am currently developing, while I get on with some crack protection, packet encryption and so on.
EDIT: No more points to be made here. Thread closed.
http://lfsbrasil.com/loja/en/
As stated many times recently, I am interested in making it harder for crackers to crack LFS. But there isn't really much point releasing the same current version with new crack protection, as the old one is still around. So crackers could say:
"Ah, I can have this version or that version of Live for Speed, which are exactly the same except one is easier to crack and one is harder... hmm, hmm, oh what a dilemma, hmm... what a difficult decision, hmm... what will I do?"
I think you get my point. What we need is a new and updated LFS that people do want to have, that also comes with better crack protection. Better not give up all actual development right now in order to work on crack protection. Eric will be able to use the new graphical tools that I am currently developing, while I get on with some crack protection, packet encryption and so on.
EDIT: No more points to be made here. Thread closed.
Last edited by Scawen, .
The setup bug is related to encryption. There was no check that the decryption was successful.
Now (since 0.6E14) the bug may still happen, but it will be detected and you will join the spectators with a light red message.
I would like to prevent the decryption bug happening but this will depend on better knowledge about how the bug comes up. The new message may help with that.
About the graphical bug with TH2GO, I am interested to know how it goes using the new Test Patch because it uses DX9 instead of DX8.
Now (since 0.6E14) the bug may still happen, but it will be detected and you will join the spectators with a light red message.
I would like to prevent the decryption bug happening but this will depend on better knowledge about how the bug comes up. The new message may help with that.
About the graphical bug with TH2GO, I am interested to know how it goes using the new Test Patch because it uses DX9 instead of DX8.
FGED GREDG RDFGDR GSFDG