Eureka Encryption Library Help
Overview
The Eureka Encryption Library allows the Linux or GNU developer to encrypt and decrypt
files and/or databases either in Text (151 character set) or Binary (256 character set)
allowing a 24-hour encrypted state for the data. This will prevent anyone from
stealing or selling your data, or the data of the consumer of your software. It can
also be used to encrypt and decrypt strings passed back and forth between applications
or within the same application.
The Text character set should handle most Western languages (English, Spanish, French, German, Itailian, Norwegian, Swedish, Finnish, etc) but
not Cryillic languages (Russian, etc), Asian, Hebrew or Arab languages.
It is extremely important to test and fully debug your code before applying it
to production files. The smallest error can render you files worthless and
unrecoverable. Be sure to move copies of the files to a test area and fully test
them prior to moving the new executable applications into the real production
environment.
Due to differences between the various application packages, you may require
modifications to the explainations presented, but the main ideas are simple
and direct enough to make whatever changes are required to be effective.
Text is defined as a 151 character set and Binary is defined as
the entire 256 character set. For most uses, Binary will suit all your needs,
while only the characters within the Text Mode can be used for Text cryptions. The
Text character set consists of the normal keyboard characters that are generally
typed (including the
Enter key). Use Binary to include
non-Text characters and also because it is much stronger to break.
A Visual Basic application EURTEST is included to illustrate all the various
call and contains the same examples described in this section.
GENERAL DEVELOPMENT PROCEDURES
To utilize these calls to their fullest potential, these steps should always be followed:
1) Perform a EurGenTextKeys or EurGenBinaryKeys before any cryptive call. You must do this before the first call is made
because it creates the data files needed to process any cryptive process. Also create a pause of about two seconds after the call so
it has time to complete if cryption immediately follows the call.
2) Perform whichever calls are required for your needs.
3) When the DLL's are no longer needed and/or when the application terminates, perform
the EurShutDown call. You may also want to perform the EurDeleteDecFiles call.
See the Procedures and Examples section
for more information on the above mentioned calls.
Back to Menu
Support and technical issues can be directed via eureka@datasecuritysolutions.com
Copyright © 1994-2000, 2002, 2003, 2005, 2007 Data Security Solutions, Inc. All rights reserved.