Tom Lane wrote:
> Dave Page <dpage@pgadmin.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@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ None of us is going to be here forever. +
