Encryption

License file and encryption explained

In order to encrypt your own content, you will need a valid license file and a hardware dongle. The dongle (WibuKey) will be sent to you by mail. To receive a LicenseFile.xml you need to provide a list of maximum 5 phone serial numbers per development platform. There is a more in depth explanation on how to receive this number for iPhone and Android. We will then create a signed LicenseFile.xml for you, where the serial numbers are listed. You now can create your own configurations and content. If you want to deploy your application, the content needs to be sent to metaio. We will then re-encrypt the content without device limitations, if you have a runtime license.

We are already working on an online tool, which should simplify this process.

Where can I find encryption tool?

The encryption tool is a single executable binary Crypter.exe on Microsoft Windows. It can be found in Tools\Encryption in the install directory, e.g. C:\Program Files\metaio\Unifeye SDK Mobile - 2.1\Tools\Encryption.

How do I encrypt my content?

In order to use your own content or tracking configuration you need encrypt these files. If you have a tracking configuration which includes a picture, like Picture Marker or Markerless Tracking, then you need to additionally encode this tracking configuration.

The following files need to be encrypted:

• TrackingData.xml: XML Tracking configuration
• model.obj: OBJ 3D file format
• model.md2: MD2 3D file format

You don’t need to encrypt the texture files.

To be able to use self-created content with UnifeyeSDKMobile, the content needs to be encrypted. For encryption a console application is shipped with the SDK Mobile installation.

The console can be used both for encrypting and decrypting model files.

encrypt TrackingData.xml LicenseFile.xml

will create a TrackingData.xml_enc file you can now load in your application. If you want to publish an application without copy protection, please contact metaio to have the copy protection removed from you encrypted files. The LicenseFile.xml will be sent to you together with the SDK installer. Please read the next section on how-to get the needed IMEI/UDID numbers for generating such a LicenseFile.xml. Also please note, supported file formats for reference images in a tracking configuration are PNG and PPM.

During loading an encrypted file the “_enc” part of the file ending is removed, in order to determine the original file name e.g. “*.xml_enc“ will be loaded as “xml” file.

Encrypting files on MacOS

Encryption on MacOS is done using an Automator action. For more information have a look here.

What is the IMEI/UDID Protection?

Together with the SDK you will receive a license file which contains a unique number per mobile phone. Every encrypted file will be bound to this unique number. For Windows Mobile and Symbian devices this number is the IMEI. You can get this number by dialing *#06#.

For iPhone, we need the UDID please read this on how to get the UDID.

Data and code will only work on mobile phones stored in the LicenseFile.xml. If you want to remove the protection mechanism from a configuration, please contact metaio.

-- SupportMetaio - 2011-03-01