On 07/15/2015 06:58 PM, Claudio Valderrama C. wrote: >> -----Original Message----- >> From: Alex Peshkoff [mailto:peshk...@mail.ru] >> Sent: Miércoles, 15 de Julio de 2015 6:41 >> >> On 07/15/2015 12:20 AM, Claudio Valderrama C. wrote: >> >>> same as the strange need of >>> using sysdba to add sysdba to complete the command: >>> >>> gsec -add sysdba -pw masterkey -user sysdba >>> >>> Alex may say that one sysdba is the embedded admin and the >> other is the user >>> that will be added to the security db, but for the common >> user this command >>> flies in the face of reason. >>> >> Claudio, your suggestions? Always run gsec as sysdba in >> embedded mode? >> But what to do with sql-based user management? > In an ideal world, things would continue running as before.
It's very easy to execute a command, adding SYSDBA to database, at security DB build step. But I think I've already explained many times here why is this solution bad. > However, since > the security model is changing, To be precise - problem we have is related first of all not to arrival of multiple security plugins with srp as default - actual problems began when we limited default rights to create objects in a database to dba. Before it adding "-user sysdba" to gsec/isql command line was not needed. Yep, that's also change of the security model, but suppose you had in mind another change. > I would like to work as before if I select > legacy authentication in the config file (no need to make special commands). > Is this doable? That is what you have now. Legacy plugin is true legacy. ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
