Skip site navigation (1) Skip section navigation (2)

Re: Problem serving one-click installer to Syria

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dave Page <dpage(at)pgadmin(dot)org>, "M(dot) Bashir Al-Noimi" <admin(at)mbnoimi(dot)net>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL www <pgsql-www(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Subject: Re: Problem serving one-click installer to Syria
Date: 2010-06-23 13:48:49
Message-ID: 201006231348.o5NDmnP19056@momjian.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-www
Tom Lane wrote:
> Dave Page <dpage(at)pgadmin(dot)org> writes:
> > So unfortunately the advice we've received is essentially identical to
> > what Josh found when working for Sun, which is that there is nothing
> > that EnterpriseDB, or the community running postgresql.org can do to
> > help without risking severe penalties.
> 
> What's not apparent to me is why the one-click installers are any
> different from the source code.  ISTM that if putting them on the
> postgresql.org mirror network would be legally hazardous, then we
> *already* have a problem.
> 
> Is it not sufficient to have mirror servers within the US block
> connections from the embargoed countries?

To follow up on this, I think the reason blocking just USA servers from
serving embargoed countries is that the installers are USA-produced,
meaning anyone who moves them from the USA to servers that can serve
Syria is subject to prosecution, even if they are not USA citizens or
work for USA companies, but simply visit the USA.

Now, technically the source code is not USA-produced but should not be
served from USA servers, though I doubt practically that is an issue.

A more concrete issue is that the Command Prompt-produced RPMs are
USA-produced and probably have the same restrictions as the EDB
installers.  I wonder if those are blocked from serving embargoed
countries, though that is really a Command Prompt issue (meaning it is
not the community's responsibility to check on such things).

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + None of us is going to be here forever. +

In response to

pgsql-www by date

Next:From: Kevin GrittnerDate: 2010-06-23 16:45:16
Subject: Re: dividing money by money
Previous:From: Greg Sabino MullaneDate: 2010-06-22 17:25:21
Subject: Re: Adjusted the hackers mailing list

pgsql-general by date

Next:From: Thom BrownDate: 2010-06-23 13:50:31
Subject: Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
Previous:From: Grzegorz JaśkiewiczDate: 2010-06-23 13:43:12
Subject: Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group