Re: Superuser without pg_hba could drop database
От | Mudy Situmorang |
---|---|
Тема | Re: Superuser without pg_hba could drop database |
Дата | |
Msg-id | AANLkTi=kshpoALrnZY3O70HhXCFvCyiP-yc=31Ys2o3a@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Superuser without pg_hba could drop database (Guillaume Lelarge <guillaume@lelarge.info>) |
Список | pgadmin-support |
Ok, Thanks for the answer.
2010/7/29 Guillaume Lelarge <guillaume@lelarge.info>
Le 29/07/2010 09:15, Mudy Situmorang a écrit :> psql runs only from the server, while pgAdmin (which is a standardWrong. psql can run from anywhere. "psql -h ip_of_the_server -U
> installation in PostgerSQL for windows) easily installed in any clients.
>
my_superuser postgres" will connect to the server if the pg_hba.conf
allows me to. And I will be able to drop any database I want.pg_hba.conf only provides *access* control, not objects' rights control.
> In a network with several different projects & many databases that requires
> dozens of superuser, pg_hba could provide the required access control.
>Sure. That's probably why you shouldn't have that many superusers.
> In this bug, when one superuser password compromised, then all database can
> be dropped from any clients using pgAdmin.
>
Having one or two is understandable. Having more is, to say the least,
weird. Not sure that you know this, but a user can be owner of a
database without being a superuser. If you have a specific owner for
each of the database, the owners won't be able to drop other databases.
They will only have the right to drop their own.You mean with every PostgreSQL admin tool. You can do that with any of
> IMO this is a major security problem on pgAdmin software.
>
them. Even psql. You can easily install psql on a PC and drop a database
if you are a superuser and have the right to connect on at least one
database. I think you misunderstand the use of the superuser. You
shouldn't have a lot of them.
--
В списке pgadmin-support по дате отправления: