| |
HTML & IMAGE ENCRYPTION - TECHNICAL INFORMATION
FILE TYPES AND SIZE SUPPORTED- Documents - HTM, HTML, TXT, CSV, PDF*, DOC*
- Images - GIF, JPG, PNG
* PDF and DOC files are converted to HTML using Lizard Protector's built in converter.
Maximum single file size that can be protected is 12MB.
OPERATING SYSTEMS SUPPORTED - Windows 2000
- Windows 2003
- Windows XP
- Windows Vista
SERVER REQUIREMENTS (FOR OWN SERVER HOSTING) The Lizard Protector administration system can be installed on either a Linux, Unix, or Windows 2003 server.
Linux Server running Red Hat, Suse, or Fedora with Apache, and MySQL 4.1 or above.
Unix Server running FreeBSD with Apache, and MySQL 4.1 or above.
Windows 2003 Server or above with MySQL 4.1 or above and SendMail or a similar program for sending emails installed (e.g. MS Exchange).
Intel Celeron 2.0 GHz or higher, 512 MB DDR RAM, 40 GB IDE hard drive (minimum spec).
The server must be capable of having Java JDK and Apache TomCat installed on it.
Supported versions are:
- JDK version 1.5 and above
- Apache Tomcat 5.0.28 and above
- MySQL 4.1 and above
Full root access is required.
A Domain name must be assigned to the server.
WEB CONTENT ENCRYPTIONWeb content is encrypted using the FIPS approved algorithm, AES at its strongest strength, 256 bit. For more information on the AES alogrithm see FIPS-197.
WEB CONTENT DECRYPTIONWeb content is decrypted on-the-fly entirely under our own control in the secure viewer.
Decrypted content is never stored to disk in temporary files or in the Windows swap file.
We do not rely upon other implementations, or plug-ins that can be subverted, or clash with plug-ins provided by other suppliers.
PUBLIC KEY TECHNOLOGY We use strong public key technology rather than weak password mechanisms that are easily crackable. Since there are no passwords to enter the system is not vulnerable to password attacks. Decryption keys are transparently relayed to the client computer and stored in encrypted format. There are no passwords to enter, manage, compromise, forget or pass on to others.
All communication between the client and the server is encrypted in order to prevent an attacker from being able to observe the secure exchanges between the client and the administration system. Where key material is being exchanged it is encrypted prior to being sent using a DH exchange at 2048 bits. This avoids the possibility of theoretical attacks where the attacker may observe in excess of 1.5 million messages.
KEY MANAGEMENT Whilst we use public key technology, no key management is required by you as the publisher or by your users or customers, as it is all handled transparently by the licensing system. There are no certificates to revoke when you want to terminate a customers access or any other PKI complexity.
LICENSE CONTROL We do not create extra files on disk that can be copied to another computer along with the protected files so they can be easily shared and viewed.
See also Our Technology on how the licensing system prevents your customers sharing their registration information and Features in Depth.
Web content encryption technology - encrypt HTML and images. Web content encryption that ensures your HTML and images are encrypted with strong encryption and DRM controls. Protect your web content without using passwords. | |
