I plan to have 3 levels of crypt requirement: disabled, enabled and required. They will work as follows (on client + server): enabled + required => crypt enabled + enabled => crypt enabled + disabled => raw disabled + required => fail disabled + disabled => raw required + required => crypt This is more or less typical approach.
What I want to advice - should we have separate crypt level setting for client and server in firebird.conf? Must say that default crypt level must be different for client (enabled) and server (required). On server it's definite security requirement, on client - compromise making it possible to attach to old servers. And in some cases it may be desired to set outgoing connections from server to something different than incoming. But may be it's just overcomplicated approach and single parameter CryptLevel is enough? ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
