AP> Well, this depends upon where the crypt key is stored. It's AP> possible to(...)
Sure, the key "is the key" :) AP> Unfortunately, that does not work for remote access. Even if we use a AP> kind of safe, encrypted channel to talk to server and pass they key to AP> it, how can we avoid installing another copy of server, which will dump AP> passed "secret" key? Does anybody knows how other Open Source databases deals with this situation (ie: MySQL/Postresql, etc)? AP> Returning to source dropping. I agree with Adriano - as soon as such AP> re-compiler is written (and this is not too hard thing to do), AP> converting BLR to SQL is trivial. I guess 99.9% of the Firebird users have no knowledge of the Firebird source and internals (otherwise I guess we would have much more code contributions than the actual "zero"), and 95% never programmed in C++, so, this is "not a hard thing to do" just for you, the core-developers :) Really, most of the users doesn't even know what BLR means. Anyway, I don't care about the syntax. Just make sure that removing the source will still be possible in future versions. It is a "false" security, but it works for most of the people. []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
