On Tuesday 20 December 2011 at 14:20 Alex Peshkoff wrote: > I wonder is it possible to change windows installer to initialize > security database.
It is possible, but I'm not sure it is practical or desirable. It would be interesting to know what percentage of deployments are for development and what percentage are for production. For development the requirement to set a password for SYSDBA will be a real pain. Obviously production deployment should require that SYSDBA does not use the masterkey password. I suspect that the solution for windows will require implementing one of the following: o provide a screen that asks user to enter new SYSDBA password. Default will be masterkey so user can click through as usual. or o Add a checkbox that allows a user to keep SYSDBA/masterkey. Default will be unchecked. If unchecked then next screen will ask user to enter new password. The latter solution will encourage more users to create a new password because most users will click through before reading the screen properly. We also need to deal with scriptable installs. For this I would suggest a command-line option that specifies the new password (which could be masterkey). If no password is provide then the installation would fail. Paul -- Paul Reeves http://www.ibphoenix.com Specialists in Firebird support ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
