Обсуждение: BUG #5786: Cannot start pgsql8 application with Previleged account (Admin account)

Поиск
Список
Период
Сортировка

BUG #5786: Cannot start pgsql8 application with Previleged account (Admin account)

От
"Jemshir A.P"
Дата:
The following bug has been logged online:

Bug reference:      5786
Logged by:          Jemshir A.P
Email address:      jamsheer.a.p@Gmail.Com
PostgreSQL version: pgsql8
Operating system:   Windows Server 2003
Description:        Cannot start pgsql8 application with Previleged account
(Admin account)
Details:

Hi Team,

We are the system administrator for the Windows server 2003 system and we
have an issue with an application running with "pgsql8". While starting the
application service, it is not getting strated if we are starting with any
account having admin rights. It is giving the common error message "Some
services will not strat if it has nothong to do". But we can strat the
service successfully with a local or domain account which is have only user
rights (Member of only users or only having user rights on the server).
Inshort the application services are starting only with under previleged
account.

Myrequirement is to start the application service with an account having
admin rights.

I have got this link which is discussing on  almost similiar situation. But
cant understand it clearly.
Kindly explain me if it is a known issue.

http://postgresql.1045698.n5.nabble.com/A-patch-to-pg-regress-for-Windows-po
rt-td2219653.html

Please guide me on this and let me know about the above error.

Your earlier reply will be higghly appreciable.

Regards,
Jemshir.A.P





In the application log of the server i can find the following even ID

Event ID - 0 Source - PostgreSQL Type - Error

Description :-

The description for Event ID ( 0 ) in Source ( PostgreSQL ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
Execution of PostgreSQL by a user with administrative permissions is not
permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromises.  See the documentation for
more information on how to properly start the server.

Re: BUG #5786: Cannot start pgsql8 application with Previleged account (Admin account)

От
"Kevin Grittner"
Дата:
"Jemshir A.P" <jamsheer.a.p@Gmail.Com> wrote:

> PostgreSQL version: pgsql8
> Operating system:   Windows Server 2003
> Description:        Cannot start pgsql8 application with
>                     Previleged account

> In the application log of the server i can find the following

> The server must be started under an unprivileged user ID to
> prevent possible system security compromises.  See the
> documentation for more information on how to properly start the
> server.

> But we can strat the service successfully with a local or domain
> account which is have only user rights (Member of only users or
> only having user rights on the server).  Inshort the application
> services are starting only with under previleged account.
>
> Myrequirement is to start the application service with an account
> having admin rights.

First off, that's a terrible idea from a security perspective.
Setting that aside, I believe that this was changed from an enforced
requirement to a strong recommendation somewhere around 8.2.  Since
a bump in number after the first decimal point is a new release in
PostgreSQL, telling us you have "pgsql8" means you could have any of
five different major releases (8.0 to 8.4).

http://www.postgresql.org/support/versioning

Since you seem to be running on 8.0 or 8.1 on Windows, you are
probably heading into a lot more trouble if you don't find a more
recent version to use:

http://www.postgresql.org/about/news.865

http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy

In any event, it should be clear to you from reading the messages
you included in your post that this is not a bug, so the pgsql-bugs
list is not the right place to post.  Please look over the
descriptions of the lists and try to pick the appropriate one for
future posts.

http://www.postgresql.org/community/lists/

-Kevin