SecurePAK

[Damon Caskey]

• What is Securepak? - Securepak is a tool that allows locking an OpenBOR module .pak file so its contents cannot be extracted by paxplode. In other words, people can play the modules, but can't look inside of them to see and get the contents (sprites, text, sounds, coding, and so on).
  
  
• Where do I get Securepak? - You don't. Securepak is not open software and is only available to a very small group of Lavalit administrators (currently SX, OrochiX, and Damon Caskey). Were either the binary or code base to be distributed, the very point of Securepak would be moot. Anyone could simply get themselves a copy and then paxplode a secured module.
  
  
• OK, then how do I get my module secured? - Submit a request to one of the above mentioned administrators. They will make arrangements to procure a copy of your module. If the module meets all requirements it will then be secured and returned to you.
  
  
• What are the requirements? - In a nutshell, the module must be street legal per copyright laws of the United States. If you couldn't sell it in a game store, then we won't secure it. In other words, every last piece of the module, from sprite, to sound, to font have to be all original or used with written permission from the legal copyright holder.
  
  Let me repeat this again. ALL of the module must be legitimately yours or used with written permission. If there is so much as one sound effect, picture, font, text, or other bit of content in the module that you do not own the rights to, your secure request will be denied.
  
  This is the only requirement. Quality, size, and content of the module are not taken into consideration, nor does it matter if the module is new, old, or an update.
  
  
• What's the point then? - Securepak allows the potential for commercial modules and protecting all original content. Simple as that.
  
  In all other cases, we believe allowing module makers to secure resources from others that they themselves do not own reeks of arrogance and hypocrisy. This includes edited resources, regardless of how extensive those edits may be. Far more importantly however, is that it would be polarizing to the community. The OpenBOR community thrives on an attitude of sharing and helping. We have witnessed the caustic effects an attitude of ownership can have in other gaming communities and want no part of it.
  
  Furthermore, having a very clearly defined and uncompromising line between what does or doesn't meet securing requirements ensures everyone is getting fair treatment.
  
  
• Are there any secured modules? - One module as of this writing is secured: Night Slashers X by BonusJZ, which does not meet the requirements for Securepak. It was secured by SX when the concept of Securepak was only a week old and securing policy had not yet been set. The mild controversy surrounding the securing of Night Slashers X was in fact partially responsible for creating a policy. We decided the most fair compromise between adhering to policy and keeping SX's word to BonusJZ was to allow it to remain secure for one year. After this time the secured Night Slashers X will be taken down and replaced with an unsecured copy.
  
  
• How to request a Mod for Securing? - Send a PM with the subject contain only the following words "SecurePAK Request" to either SX, DC or OX.  We will communicate via the LavaLit's Chat system or IM/E-mail.  The unencrypted files should be email to us to be secured.  We will evaluate the contents of the Module.  Once it has passed our inspection we will email you back the SecuredPak file and then you are free to upload you mod to our DownLoad Management Area.
  
  Lastly, ALL data should be password encrypted during transmission.