| Greg Fenton 2005-04-14, 9:24 am |
| Please, always post the version and build number of ASA that you are
using (e.g. "dbeng9 -v" for ASA 9.x).
Also, it would be very helpful to know what your target platform and
what remote db you are going to use (ASA, ASA on CE, UltraLite?).
Answers to some of these questions vary based .
> 1. What are the pros and cons beween simple encryption and
> strong encryption.
Simple encryption simply "obfuscates" the data. Any one with a small
amount of cryptographic knowledge (or some freely available hacker
tools) would likely be able to decypher your data.
Strong encryption is very secure. It takes (on average) somewhere in
the order of tens of thousands of CPU *years* to crack. However there
is a performance hit to having to encode/decode the data (the actual
performance hit depends widely on the types and volumes of data).
>
> 2. How would I manage the keys if I chose to use strong
>
This widely depends on how the database itself is being used. If this
is a single-user application, then one way is to treat the encryption
key as the user's "password". They should never, ever give it out.
Describe what you mean by "manage the keys".
> 3. How would I deploy stong encrypting on each remote
> database?
See above.
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
|