| |
TECHNICAL INFORMATION FOR ENCRYPTING HTML CODE
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.
HTML & IMAGE SECURITY WITHOUT PASSWORDS
Protector Web Content Security ensures the best security for your web based content. Your protected files are locked to individual computers and cannot be shared. Unlike weak and unmanageable password mechanisms Protector Web Content Security uses public key technology with strong AES 256 bit encryption, DRM (digital rights management) controls, and a real-time web based licensing system. There are no passwords to send, enter, manage, forget, or pass onto others.
You protect your web based content on your own computer. The source (unprotected) files are never exposed to a web server where they could be easily compromized. We never have access to either your original files or your protected files.
WEB CONTENT ENCRYPTION Web 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.
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 MANAGEMENTWhilst 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.
SECURE WEB PAGE VIEWER
Protector Web Content Security uses its own decryption application, a Secure Web Viewer, rather than relying on a plug-in to present your protected web content. Protected web content is decrypted in the secure viewer software which applies the necessary DRM controls and ensures your web content cannot be compromised by other applications or by common browser flaws, bugs and cracks.
Your security is not compromised by plug-in failures or conflicts. In fact, we think that plug-ins are potentially so insecure that we prevent them from loading so they can't compromise security.
Protected web content is decrypted on-the-fly in memory. It is never saved to disk in temporary format or to the Windows swap file. We do not create extra files on disk that can be copied to another computer along with the protected web content files so they can be easily shared and viewed.
To stop your protected web content being readily stolen whilst displayed on screen, the use of Windows print screen and screen grabber applications are prevented whilst the secure Protector viewer is running.
See also our DRM Technology on how the licensing system prevents your customers sharing their registration information and HTML Security Features in Depth.
| |
| |
