UltraLite User's Guide
Designing UltraLite Applications
Configuring and managing database storage
By default, UltraLite databases are unencrypted on disk and in permanent memory. Text and binary columns are plainly readable within the database store when using a viewing tool such as a hex editor. Two options are provided for greater security:
Obfuscation Obfuscating databases provides security against straightforward attempts to view data in the database directly using a viewing tool. It is not proof against skilled and determined attempts to gain access to the data. Obfuscation has little or no performance impact.
For more information, see Obfuscating an UltraLite database.
Strong encryption UltraLite database files can be strongly encrypted using the AES 128-bit algorithm, which is the same algorithm used to encrypt Adaptive Server Anywhere databases. Use of strong encryption does provide security against skilled and determined attempts to gain access to the data, but has a significant performance impact.
| Caution If the encryption key for a strongly encrypted database is lost or forgotten, there is no way to access the database. Under these circumstances, technical support cannot gain access to the database for you. It must be discarded and you must create a new database. |
For more information, see Encrypting an UltraLite database, and Changing the encryption key for a database.
Obfuscating an UltraLite database
Encrypting an UltraLite database
Changing the encryption key for a database
Using the encryption key on the Palm Computing Platform