Subject | RE: [Firebird-Architect] Dear Wryly: Security Architecture |
---|---|
Author | Leyne, Sean |
Post date | 2004-02-14T20:22:39Z |
Jim,
(Have to run out right now, but wanted to get give a quick reply for one
point)
Nothing says that the header page of a database can't be reserved as an
unencrypted page!
To be used to store the information related to the "configuration" of
the database -- its encryption and security methods/access settings.
The rest of the database could be encrypted.
Sean
p.s. Given the overhead of encryption/decryption I would suggest that
not every page in a database would be encrypted -- why would we encrypt
a pointer page???
(Have to run out right now, but wanted to get give a quick reply for one
point)
> Besides, how an encrypted database read itelf to find its decryptionCome Jim ;-)
> data? Answer: it can't.
Nothing says that the header page of a database can't be reserved as an
unencrypted page!
To be used to store the information related to the "configuration" of
the database -- its encryption and security methods/access settings.
The rest of the database could be encrypted.
Sean
p.s. Given the overhead of encryption/decryption I would suggest that
not every page in a database would be encrypted -- why would we encrypt
a pointer page???