Commented by: @pavel-zotov

One more sample: now login starts with two DOUBLE quotes (and is enclosed in one else d.q. itself :)).
Consider following batch:

@Rem -------------------------- Add user using SERVICES -----------------

fbsvcmgr localhost:service_mgr user sysdba password masterkey action_add_user dbname C:\MIX\firebird\fb30\security3.fdb sec_username """fsvc_1" sec_password 1
fbsvcmgr localhost:service_mgr user sysdba password masterkey action_add_user dbname C:\MIX\firebird\fb30\security3.fdb sec_username """fsvc_2" sec_password 1

fbsvcmgr localhost:service_mgr user sysdba password masterkey action_add_user dbname C:\MIX\firebird\fb30\security3.fdb sec_username "fsvc_1" sec_password 1
fbsvcmgr localhost:service_mgr user sysdba password masterkey action_add_user dbname C:\MIX\firebird\fb30\security3.fdb sec_username "fsvc_2" sec_password 1

echo set count on; set width uname 31; ^
select row_number()over(), sec$user_name uname, char_length(trim(sec$user_name)) ^
from sec$users where sec$user_name containing 'fsvc_'; | isql /:e30

fbsvcmgr localhost:service_mgr user sysdba password masterkey action_display_user dbname C:\MIX\firebird\fb30\security3.fdb sec_username """fsvc_1"
fbsvcmgr localhost:service_mgr user sysdba password masterkey action_display_user dbname C:\MIX\firebird\fb30\security3.fdb sec_username """fsvc_2"

fbsvcmgr localhost:service_mgr user sysdba password masterkey action_display_user dbname C:\MIX\firebird\fb30\security3.fdb sec_username "fsvc_1"
fbsvcmgr localhost:service_mgr user sysdba password masterkey action_display_user dbname C:\MIX\firebird\fb30\security3.fdb sec_username "fsvc_2"

@Rem -------------------------- Add user using ISQL cmd -----------------

echo create user """isql_1" password '1'; | isql /3333:e30
echo create user "isql_1" password '1'; | isql /3333:e30

echo create user """isql_2" password '1'; | isql /3333:e30
echo create user "isql_2" password '1'; | isql /3333:e30

echo set count on; set width uname 31; ^
select row_number()over(), sec$user_name uname, char_length(trim(sec$user_name)) ^
from sec$users where sec$user_name containing 'isql_'; | isql /:e30

Its output please see in attached .zip.

Commented by: @pavel-zotov

And for dessert:

case-1:
#⁠#⁠#⁠#⁠#⁠#⁠

fbsvcmgr localhost/3333:service_mgr user sysdba password masterkey action_add_user dbname C:\MIX\firebird\fb30\security3.fdb sec_password 123 sec_username "qwe""%\a"

C:\MIX\firebird\QA\fbt-repo\tmp>echo show users; | isql localhost/3333:e30
Users in the database
0 QWE"%\A 1 #⁠SYSDBA

-- here all fine (if not pay attention UPPERCASE of resulting characters; creating user by ISQL command will store this login with exact matching).

case-2:
#⁠#⁠#⁠#⁠#⁠#⁠

fbsvcmgr localhost/3333:service_mgr user sysdba password masterkey action_add_user dbname C:\MIX\firebird\fb30\security3.fdb sec_password 123 sec_username "qwe""%\"

C:\MIX\firebird\QA\fbt-repo\tmp>echo show users; | isql localhost/3333:e30
Users in the database
0 QWE"%" 1 #⁠SYSDBA

Where is trailing back-slash ? ( original login is: qwe""%\ -- without enclosing d.q.)
Why login contains now TWO double quote characters ? (second `"` is last byte of login; from where it appeared ?)
Why percent sign has "moved" between two double quotes ?

Commented by: @AlexPeshkoff

Pavel!
Please try to use this small echo program for windows (in a.zip) to see what gets into C/C++ routine when you type too many quotes in command line.
Also take into an account that services use gsec utility to manage users. And that gsec has very limited parser of quoted strings (being legacy intebase utility).
I suppose that after taking all that into consideration you would like to close this ticket as "Won't fix" yourself.

Commented by: @pavel-zotov

Alex,

1) was this .exe created for 64 bit Windows ?
2) samples with logins that are shown above was found by script that did generate them on random basis. Am I correct that all such 'random-generated' logins must be specified WITHOUT single or double quotes ion order to avoid such problems ? If yes, this should be explicitly reflected in doc, IMO.

Commented by: @AlexPeshkoff

1. file ec.exe
ec.exe: PE32 executable (console) Intel 80386, for MS Windows

2, An issue with quotes is not firebird issue, it's primarily OS documented behavior. What about cases when gsec is using 'original' way to work with quoted identifiers I see no big reason to document it - utility is already deprecated and we have documented that we recommend to use SQL to manage users. gsec & services are just for backward compatibility, and it's behavior re quotes did not change in fb3.

Commented by: @pavel-zotov

> services use gsec utility to manage users. And that gsec has very limited parser of quoted strings (being legacy intebase utility).
Yes, you're right: ticket can be closed with resolution "Won't fix".