Re: Minimising windows installer password confusion
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Dave Page <dpage@pgadmin.org>
Cc: Craig Ringer <craig@postnewspapers.com.au>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Sachin Srivastava <sachin.srivastava@enterprisedb.com>, Ashesh Vashi <ashesh.vashi@enterprisedb.com>, Dharmendra Goyal <dharmendra.goyal@enterprisedb.com>
Date: 2012-06-14T16:38:54Z
Lists: pgsql-hackers
On Thu, Jun 14, 2012 at 11:59 AM, Dave Page <dpage@pgadmin.org> wrote: > On Thu, Jun 14, 2012 at 11:43 AM, Dave Page <dpage@pgadmin.org> wrote: >> >> I'll have a play with it and see if a simple switch to NetworkService >> seems feasible. > > OK, I worked up a patch which uses "NT AUTHORITY\NetworkService" as > the service account by default. This doesn't need a password, so > allows us to simply prompt during installation for the superuser > password for the cluster, and not at all during upgrade. If you run > the installer from the command line with "--serviceaccount postgres" > (or some other account name), you get the current behaviour. > > I've posted it on our internal ReviewBoard system for the rest of the > team to review and test on various platforms (I've only tried it on XP > so far). Now would be a very good time for people to yelp if they > think this is a bad idea (the only downside I can see if accessing > files for server-side copy etc, but users that want to do that can > install with a non-default account). If we go ahead, we'll include it > in 9.2. What happens if they try to use this to upgrade from the EDB 9.1 installers? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company