ExtProtect v0.1.0.0 Beta Released

How is ExtProtect better?
1) It stores an encrypted backup that can be used to easily unprotect maps if you remeber the password.
2) Easy to use interface.
3) If you don't want to store a backup (because they make the map ~12% bigger), you can just leave the pasword fields blank and the map will actually shrink in size.
4) It is the first map protector that obfuscates the JASS script to make it more difficult to edit.

You can download it here
http://extprotect.psychosanity.com/

Screenshot:

wow, good job. Very nice proggy. I just have one small suggestion:

Warn the user if the map is currently protected using another protection method and this way he can't protect it with ExtProtect.
Maybe use a small label with "Green- Map can be protected" or "Red-Map is already protected using another method".

My program attempts to detect another protection method and if it detects one, it changes the text of the protect/unprotect button to "No Backup", which indicates that the map is already protected but can not be unprotected because there is no backup stored in the map. The readme clearly states that.

Also, At the request of atRandom on the UMSMaps forums, I've removed the region thing so now it WE simply says it cant open the map. The new version (Beta 0.1.0.1) is now available for download at the same URL as the previous version, and the security of the protection has not been compromised because of the change.

http://extprotect.psychosanity.com/

hehe us UMS'ers are starting to make our mark on the world! :ggani: :////

I accidentally left some debugging code in, and there was a small error introduced along with the code changes to make it not crash WE.

I've think I've fixed it, and I've uploaded a new version (Beta 0.1.0.2) which you can get at the same URL as always - http://extprotect.psychosanity.com

Sounds good - but about the backups:

If you encrypt it, you had better encrypt the DATA: If you dont then you can easily figure out the filename with SFMPQAPI.

My map protector with a password worked nicely, BUT it relied on the backup having a diff filename every time, since It only modified the filename, and not the WTG itself.

The way the backup works is that it adds all the files to be backed up to an archive (and they are compressed inside the archive to make it take up less space) and then the entire archive is encrypted with Rijndael using the supplied password and then added to the map file. The same name is used for the backup every time, but the data is encrypted with an algorithm that the US govnenment trusts, so I think its pretty secure =-)

The way the program knows you tried to use an incorrect password when unprotecting is that if you dont use the right password, the unencrypted data won't be the right format (since data unencrypted with the wrong password ends up being just jibberish).

You realize that compressing it before putting it into the map is pointless, as MPQs already compress the files, and probably more effeciently?

Actually, there is a very good reason to compress it in the archive and then put the encrypted archive into the MPQ: namely that encrypted data compresses VERY poorly. About MPQs compressing better: While it might be true that MPQs compress better than many other format (maybe, maybe not, I dunno), it is irrelevant because the type of archive I use is an MPQ.

Do you guys realize that this program breaks the EULA?

It clearly says that you can't 'own' a map or anything made by the World Editor, and that all maps should be able to be accessed by everyone? (That is the whole point of the editor)

If that is the case, would you please contact blizzard about it and ask them to tell me that at my extprotect address ([email protected])? Somebody on the battle.net forums suggested that as well, but it wasn't a blizzard employee so I'm not sure they are correct. If blizzard tells me that it violates the EULA/TOU, then I know for sure and can take whatever actions are appropriate.

I can't help you contact Blizzard, you must do that yourself.. they will never mail to anyone that someone is referring to.

If you read the EULA.. hmm, I think it's at the bottom.. you will see a paragraph about ownership. This is why Warcraftiii.net removed all protected maps from their archives.

But, I could have misunderstood the paragraph and so could wc3.net, check it out yourself first and decide whether or not it's breaking it.. after all, everything they will do is ask you to remove the software when they notice.

I am a programmer, not a lawyer. I lack the skills needed to interpret the legal documents. If Blizzard wants me to take my program down and stop distribution of it, they will have to tell me. I think that if you report my program to them as a violation and include my email address that they would contact me if my program violates anything I agreed to to play the game. As I do not wish to take it down, I will wait until they inform me that such action is required of me before doing so.

The only thing I see about ownership is this:

2. Ownership. All title, ownership rights, and intellectual property rights in and to the Program and any and all copies thereof (including, but not limited to, any titles, computer code, themes, objects, characters, character names, stories, dialog, catch phrases, locations, concepts, artwork, animations, sounds, musical compositions, audio-visual effects, methods of operation, moral rights, any related documentation, and "applets" incorporated into the Program) are owned by Blizzard Entertainment or its licensors. The Program is protected by the copyright laws of the United States, international copyright treaties, and conventions and other laws. All rights are reserved. The Program contains certain licensed materials, and Blizzard's licensors may protect their rights in the event of any violation of this Agreement.

Which doesn't mention the editor or files at all as far as I can tell, but as I said, I'm not a lawyer. Not only does it not mention files, it doesn't mention files created by other people. Even if it did, it seems unlikely that Blizzard could legally restrict others from modifying their own files.

There was a bug that would prevent some maps from opening in the world editor after being unprotected. It has been fixed and Beta 0.1.0.3 is now available at http://extprotect.psychosanity.com