Re: Heroku early upgrade is raising serious questions

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Michael Meskes <meskes(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, damien clochard <damien(at)dalibo(dot)info>, "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Heroku early upgrade is raising serious questions
Date: 2013-04-09 17:59:29
Message-ID: 20130409175929.GU4361@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

* Andres Freund (andres(at)2ndquadrant(dot)com) wrote:
> Also, it changes how privileged the people that get access to the
> vulnerability are. If they are allowed to install at the same time as
> everyone else its somewhat fair game, otherwise there will be people
> making a marketing distinction out of their privileged access.

I do not consider this a game where everyone should be treated 'fairly'
wrt their exposure to attackers. I would be open to including something
in the policy which discourages members from advertising their
membership as a marketing distinction, but I'm not convinced that it's
necessary.

Thanks,

Stephen

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Stephen Frost 2013-04-09 18:01:32 Re: Heroku early upgrade is raising serious questions
Previous Message Stephen Frost 2013-04-09 17:54:08 Re: Heroku early upgrade is raising serious questions