Subject | Security: restricting access |
---|---|
Author | h_urlaf |
Post date | 2004-03-03T18:21:43Z |
Hi all,
The FB superserver I intend to run will be accessed by other machines
running client software. From a security POV, I'd like to know if the
following is possible:
* Allow only ZeBeDee connections, no plaintext connections (although
localhost-only would be OK)
* Restrict the remote clients from inspecting security.fdb
* Restrict the remote clients from backing up my database(s)
* Restricting the remote clients from creating new databases or tables
in existing databases.
Some of the client software connecting would be 'semi-trusted', so I'd
like to curtail the operations they can perform. I would create
separate DB accounts for these connections.
Emiliano
The FB superserver I intend to run will be accessed by other machines
running client software. From a security POV, I'd like to know if the
following is possible:
* Allow only ZeBeDee connections, no plaintext connections (although
localhost-only would be OK)
* Restrict the remote clients from inspecting security.fdb
* Restrict the remote clients from backing up my database(s)
* Restricting the remote clients from creating new databases or tables
in existing databases.
Some of the client software connecting would be 'semi-trusted', so I'd
like to curtail the operations they can perform. I would create
separate DB accounts for these connections.
Emiliano