This is an issue (and one that I brought up). I don't think it important. Somebody does need to specify a key to read an encrypted instance, but while that key is active, i.e. attachment session, it won't be able to read unencrypted instances. Personally, I think this is a feature -- different vendors can encrypt their sources with different keys in the same database. But other people might feel differently.
> On Sep 1, 2014, at 10:55 AM, Mark Rotteveel <m...@lawinegevaar.nl> wrote: > > On Mon, 1 Sep 2014 09:22:37 -0400, James Starkey <j...@jimstarkey.net> > wrote: >> If the key is wrong, the engine will return horrible, useless gook. It >> would be possible to check for ascii/utf-8, but this would defeat other >> uses of the mechanism. So return horrible, useless gook. > > However, what if I want only part of my source columns encrypted (eg the > sensitive parts), and the rest not (eg customer stored procedures; or > things the vendor doesn't want to hide). Just indiscriminately trying to > apply the key to encrypt would mean that also things I don't want to hide > get encrypted, and when applying to decrypt would make unencrypted source > code unreadable. > > Mark > > ------------------------------------------------------------------------------ > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
