Search Postgresql Archives

Securing Postgres

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Example: On a MS Windows Server with MS SQL Server. The administrator with the administrator username and password can not access the SQL server data. He also needs the SA username and password for the SQL server to do so. He can stop and start the server and so on but not access the data.

How do I secure a system in the same way with Linux and PostgreSQL.

Richard Huxton wrote:

L van der Walt wrote:

I would like to secure Postgres completly.

Some issues that I don't know you to fix:
1.  User postgres can use psql (...) to do anything.



Prevent anyone from logging in as user postgres.
Remove psql.

2.  User root can su to postgres and thus do anything.



That's the root user - it is supposed to be able to do what it likes.

3. Disable all tools like pg_dump



You can delete the executables, but that's not going to stop people running their own version if they can connect.

How do I secure a database if I don't trust the administrators.
The administrator will not break the db but they may not view
any information in the databse.



If you don't trust the administrators of the machine, there's nothing you can do if they have physical access to it. They'll always be able to work around anything you can do.

Can you say more about the situation - it might be someone has been in a similar situation themselves?
--
  Richard Huxton
  Archonet Ltd






---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux