On 08/31/14 23:23, James Starkey wrote: > Let's try another tack on this problem. What is the best possible way to > solve it if schedule were not a problem? And is this a special case of a > more general problem? > > Here's an idea to get the creative juices working: Suppose the database > parameter block were extended with a composite containing quadruples of > <schema, table, field, key>, and if given, instances of the given field > would be encrypted and/or descripted with the given key. This would be > robust, defensible security for any field and would be easy to implement in > both database tools and the database engine, and would have no impact on > system tables, the API, or transmission layers. Carlos would be happy, the > hard-security guys would be happy, and the mechanism would generalize to > user as well as system tables. > > This is a starter solution. There must be many more lurking out there. >
But what prevents anyone to use that present in database key to decrypt procedure code and watch it? ------------------------------------------------------------------------------ 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
