From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Cc: | "Darko Prenosil" <Darko(dot)Prenosil(at)finteh(dot)hr>, <pgsql-hackers-win32(at)postgresql(dot)org> |
Subject: | Re: PgSQL not as Administrator - probs on w |
Date: | 2004-07-09 12:21:29 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE34BE31@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
> > In the win32 user's sight, the current implementation is very
> > dogmatic. While there *has* to be some dogmatism about
> security, IMHO
> > in the case of account to run pgsql on this is up to the
> > administrator, not us. We should recommend using a separate user,
> > support it in the installer by default as comfortable as
> possible, but
> > enforcing it is regarded as non-native and thus suspicious in the
> > win32 world.
> >
> > Running as admin is so common for Windows, you'd never see
> complaints
> > about that aspect. Even programs *requiring* admin rights
> are widely
> > accepted (with some minor grumbling).
> >
> > It's another universe...
> >
>
> I originally left the 'running as root/administrator' check
> out of initdb for this reason.
Initdb opens a pipe to postgres.exe, no?. Which makes that kind of a
non-op, since it will just fail at a later time...
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Tibbett | 2004-07-09 12:27:19 | Re: PgSQL not as Administrator - probs on w |
Previous Message | Andrew Dunstan | 2004-07-09 12:14:55 | Re: PgSQL not as Administrator - probs on w |