|
|
|
|
|
Although Cryptor 4.0 has been superseded by its big brother Cryptor 5.0 it is still as relevant today as it was in 1998 when first released. It sports the precursor to the Cryptor 5.0 hooking technology enabling it to integrate seamlessly with modules in a process under Windows 9x, Windows ME, Windows NT 4.0, Windows 2000 and Windows XP. Like its predecessors Cryptor IV transparently and selectively encrypts / decrypts " on the fly" by intercepting the data as it moves from the disk to the registered application and vice versa - so the data on the disk is always encrypted. Unauthorized users will see a completely scrambled and meaningless file. There are no alternative keys - only the password will give normal access. Cryptor 4.0 is a 32Bit DLL supporting Win95, Win98, WinME, WinNT, Win2K and Windows XP. There are no drivers, services or VxD's to distribute with your product, just the one convenient self contained DLL. (VFP users can use the DLL directly or use the specially provided FLL API Libraries to access the DLL with a familiar backward compatible interface). Cryptor IV is a true 32Bit solution re-engineered with no 16bit throwbacks therefore protecting the performance gains you expect from your 32bit software and hardware investments. What development platforms can I use Cryptor IV with ?Cryptor IV can be used from the following development platforms :
These are the ones we've tried so far ! How secure is Cryptor IV encryption ?Cryptor IV contains the same powerful encryption algorithm used in earlier versions. These earlier products gained the reputation as the most secure encryption product available for FoxPro, by FoxPro users. Previously subject to export restrictions, the algorithm has now had these lifted. Is Cryptor IV compatible with previous versions ?Absolutely, Cryptor IV was developed with backward compatibility in mind. It supports files encrypted with Cryptor versions 1.80 and upwards. What code changes do I have to make to incorporate Cryptor IV ?Cryptor can selectively encrypt any file that your program uses directly. Once Cryptor has been initialized and the encrypted files have been successfully registered, there are no further program changes required. Depending on how you organize your encrypted files the code changes can be as small as adding one line of code, total !!! The initial encryption of an existing unencrypted file requires use of the CRYUtl_Encode function passing the filename and a password. Subsequently, the Cryptor IV registration function CRYMan_Register with the same parameters will enable 'normal' access to the file by your application although the file is still encrypted on disk !
|
Copyright © Xitech (Europe) 2005 All rights reserved worldwide. |