Issue Details (XML | Word | Printable)

Key: CORE-1806
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Vitezslav Svejdar
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
Firebird Core

GSEC used remotely

Created: 27/Mar/08 12:18 PM   Updated: 27/Mar/08 12:18 PM
Component/s: None
Affects Version/s: 2.1 RC2
Fix Version/s: None

Environment: Windows XP

 Description  « Hide
Dear developers.

It seems that what is written in in the second par of p. 12, viz:

"The version of gsec provided in Firebird 2.0 can be used to maintain the security database on previous versions
of Firebird and it is hoped, Interbase from version 6.0 upwards"

does not work for me.

My testing FB 2.1 RC2 installation is installed manually from zip, the service was activated using instsvc with
parameter -n "FB 2.1" and it is listening on port fb21 (which translates to 3052 in the services file).
Its home directory is c:\Program Files\Firebird\Firebird_2_1.
There are two other paralel instances of Firebird, FB 2.0 listening on port fb20 and FB1.5 having no special information
about port in firebird.conf, and thus listening on 3050.

After cd "c:\Program Files\Firebird\Firebird_2_1\bin", the commands
gsec -da "localhost/fb21:c:\Program Files\Firebird\Firebird_2_1\security2.fdb" -user sysdba -pa masterke
gsec -da "localhost/fb20:c:\Program Files\Firebird\Firebird_2_0\security2.fdb" -user sysdba -pa masterke
work normally for me, i.e. allow me to modify users in one or the other security database.

However, after the command
gsec -da "localhost/3050:c:\Program Files\Firebird\Firebird_1_5\security.fdb" -user sysdba -pa confidential
gsec does show its prompt (so it has verified the different password), but then hangs if I say "di"
or "add fb15 -pw fb15".

Similar (i.e. wrong) behavior is experienced if I try to modify users in some other FB 1.5 Windows installation,
which is "really remote", outside the local network.

Thank you for the work on Firebird project. All the best, Vitek

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.