On Wed, 03 Mar 2010, Enrico Maria Giordano wrote: Hi,
> Dear friends, is there any technical reason why DBI_PASSWORD can't > be used to crypt DBFs with memo fields? Even leaving memo fields > uncrypted while crypting all the other fields would be welcome. This encryption was added for SIX3 compatibility. In original implementation it encrypts DBF and MEMO files leaving indexes as is. When I begin to make real life test of SIX3 behavior I found many very serious bugs in memo encryption. I couldn't replicate them to be bug compatible and keep binary compatibility because in some cases they caused data corruption so finally I decided to commit only DBF part encryption and block any encryption for tables having memo files to reduce the chance for data corruption/lost when tables are shared with programs using original SIX3 RDDs. It's possible to unblock memo encryption quite fast in current Harbour code. Anyhow if we begin to create such encrypted files then it will be necessary to keep this code for backward compatibility. Otherwise users lost their data after upgrading to newer versions and it's the reason why I do not want to make it without good analyze. I planed in some spare time to document all anomalies and bugs in SIX3 memo encryption and try to find a method which will allow at least in some limited way to share data with SIX3 encrypted memo files. So far I haven't do that and I do not know if I'll ever try. Probably I'll create new much stronger independent encryption method for Harbour only which will encrypt table, memo and also index files without any limitations caused by more or less strict compatibility with some other products. best regards, Przemek _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
