Would be great to provide an Optional archive encryption with WRS resource packer using AES-192 or AES-256, except of source code the rest can very easily be decompressed.

Thanks in Advance!

In Lite-C there should be no source code in the WRS at all, because it's all precompiled.

It will be decrypted in RAM anyways, so for one the key has to be saved somewhere and could be read from there, or the wanted assets could just be dumped from RAM.
DRM does not and will never work.

We know.
However, licenses for models like from Dexsoft usually require a certain encryption. No one ever talks about the strength of the encryption or that you should use a peer reviewed implementation that doesn't fall apart from the first side channel attack, but that's why they are artists in the first place

Speaking of, AES-192 and AES-256 implementations in shipping software requires you to have approval from the Unites States (the BIS to be specific) and that you annually report to two US government agencies (every January), at least if you want to export your software from the US (read: If your program comes from an US server, even if you are a citizen of the EU, you need an ERN authorization).

Further reading: http://www.bis.doc.gov/index.php/policy-guidance/encryption/identifying-encryption-items

tl;dr: Cryptography stops being fun once you realize that the United States Government is part of the world
(hey, want to hear a fun story? When I had a layover in the US (read: I never left the airport!) two weeks ago, I had to leave fingerprints of all of my fingers, had a picture of me taken and my luggage searched. At least I got a few Department of Homeland Security stickers on some of my stuff)

If it's about artwork of artists I guess the goal usually is to make their work non directly reusable.
Means you won't need a super duper bulletproof encryption, but just something that makes sure the artowrk cannot be used out of the box by anyone having installed your game (like it is possible without WRS).
Some shabby byte twister thing and add_buffer() should do.

Afaik is the Advanced Encryption Standard free to use.


But i've some other ideas to secure it in 99.99%

It's not about licensing but about export restrictions. Huge difference.

That means if i'll export it from my server in Germany it would be free, right?

It's free either way. But yes, you are not bound by US export laws in Germany.
However, the second you switch to an US based server, or actually are a US citizen, you are fall under their restriction and export laws.

I don't think putting AES wrs resource support into Gamestudio is a good idea, for that specific reason: Gamestudio has a lot of people from the states using it, and there is a Conitec office in the states as well, which I don't know how much it is involved in Gamestudio... IANAL, but so aren't most Gstudio users, and I don't think it's in Conitecs interest to get US users, or people with servers in the US, into trouble. I mean, just sell your stuff on the Windows or Android market place, or use Akamai as your CDN: You may end up no longer being allowed entry in the US (or get a bunch of police knocking on your door).

If you want resources protected by AES: Implement it yourself (no, don't. Seriously, don't. Use a crypto library with a known track record). I wouldn't trust an implementation by Conitect to begin with, no offense, and you should be able to just do it yourself using add_buffer() and a wrapper over some crypto library (for example CommonCrypto or OpenSSL)

Just out of curiosity, why would you want to do that?