Of course, when the rows are inserted / updated, the
changes are also reflected in the .log file in a clear text
format and stay there until a CHECKPOINT is issued. But the
patch works for sending properly shutdown confidential
databases around.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could this be re-submitted again the current CVS baseline so
that someone can incorporate it into the main development
branch.
Also has anybody thought about encrypted database files i.e.
when the database is run as a server the db admin starts the
database with a passphase and then all the data files that
appear are encrypted for added security. It would mean the
clients don't change but the database files are encrypted not
cleartext as they are currently. This would mean that
nobody could look at the datafiles and bypass the db login
mechanism.
Cheers
Matt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ZIP file containg modified source and documentation
Logged In: YES
user_id=150940
A useful addition that many users have asked for.
Of course, when the rows are inserted / updated, the
changes are also reflected in the .log file in a clear text
format and stay there until a CHECKPOINT is issued. But the
patch works for sending properly shutdown confidential
databases around.
Logged In: YES
user_id=1029771
Hi,
Could this be re-submitted again the current CVS baseline so
that someone can incorporate it into the main development
branch.
Also has anybody thought about encrypted database files i.e.
when the database is run as a server the db admin starts the
database with a passphase and then all the data files that
appear are encrypted for added security. It would mean the
clients don't change but the database files are encrypted not
cleartext as they are currently. This would mean that
nobody could look at the datafiles and bypass the db login
mechanism.
Cheers
Matt