> > Again, I feel that they issue of client/server connection encryption and > database encryption are being co-mingled. > > > > Database encryption is about the engine's ability to access/work with a > database, there should be absolutely no client dependency. > > More than 80% of encryption cases are expected to be applications > distributed together with databases. They are usually single-user and often > use the embedded Firebird. In this case it's really logical to allow the > client > application to manage the key.
Then, this is solution should be described in the context of how the embedded engine will support encryption. This thread was about SS/other engines. Are you saying that the only mode that database encryption will work, is the one which satisfies only 80% of the installs? What solution is proposed for the other 20%? How would ODBC/JDBC connections to an encrypted database using an embedded engine work in the proposed solution? Sean ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel