[liberationtech] Blue Coat and Syria

Collin Anderson collin at averysmallbird.com
Thu Oct 13 11:32:39 PDT 2011


I would note that many of Treasury's sanctions are overzealously interpreted
by American companies to include things that they specifically do not. OFAC
Regulations were revised last year (regarding Iran: §560.540; Cuba and Sudan
in name elsewhere; presumable Syria too) to permit the export of information
services and software to embargoed countries provided it is done so 1.) at
no cost to the user 2.) without direct or indirect knowledge of government
use.

Documenting misapplications of the law is a campaign in its nascent stages,
which I should reach out to the mail list about in another thread.

GSoC, I assume, is other matter originating in the stipend.

Cordially,
Collin

On Thu, Oct 13, 2011 at 2:16 PM, Jillian York
<jyork at cyber.law.harvard.edu>wrote:

> Regulation that forces transparency (e.g., a licensing scheme) seems to be
> a popular theme these days and frankly, I'm personally behind the idea.
> When we have export regulations preventing Syrians from getting access to
> basic tools like Google Chrome and Java and unable to participate in Google
> Summer of Code because "oops, someone might accidentally give them a
> t-shirt", but those same Syrians are being hampered by American tools from
> Bluecoat, something is terribly wrong.
>
> -JCY
>
>
>
> On Wed, Oct 12, 2011 at 3:11 PM, <liberationtech at lewman.us> wrote:
>
>> On Wed, Oct 12, 2011 at 12:19:36AM -0400, jacob at appelbaum.net wrote 2.1K
>> bytes in 61 lines about:
>> : The sale and support of surveillance equipment should be regulated like
>> : firearms.
>>
>> Careful here. More bureaucracy is rarely the answer to a problem. More
>> transparency is a fine first step. Who sold what to whom would be good
>> to know now. Who supports whom would be good to know as well.
>>
>> Regulating firearms has done little to stop the global weapons trade, in
>> fact it's just created a huge underground market that lacks
>> transparency. At least this is what those who monitor this sort of thing
>> tell me.
>>
>> This appears to be the same problem we have now with network
>> surveillance and control equipment.
>>
>> --
>> Andrew
>> pgp key: 0x74ED336B
>> _______________________________________________
>> liberationtech mailing list
>> liberationtech at lists.stanford.edu
>>
>> Should you need to change your subscription options, please go to:
>>
>> https://mailman.stanford.edu/mailman/listinfo/liberationtech
>>
>> If you would like to receive a daily digest, click "yes" (once you click
>> above) next to "would you like to receive list mail batched in a daily
>> digest?"
>>
>> You will need the user name and password you receive from the list
>> moderator in monthly reminders.
>>
>> Should you need immediate assistance, please contact the list moderator.
>>
>> Please don't forget to follow us on http://twitter.com/#!/Liberationtech
>>
>
>
>
> --
> jilliancyork.com | @jilliancyork | tel: +1-857-891-4244
>
>
>
>
> _______________________________________________
> liberationtech mailing list
> liberationtech at lists.stanford.edu
>
> Should you need to change your subscription options, please go to:
>
> https://mailman.stanford.edu/mailman/listinfo/liberationtech
>
> If you would like to receive a daily digest, click "yes" (once you click
> above) next to "would you like to receive list mail batched in a daily
> digest?"
>
> You will need the user name and password you receive from the list
> moderator in monthly reminders.
>
> Should you need immediate assistance, please contact the list moderator.
>
> Please don't forget to follow us on http://twitter.com/#!/Liberationtech
>



-- 
*Collin David Anderson*
averysmallbird.com | @cda | Washington, D.C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/liberationtech/attachments/20111013/06671a3d/attachment.html>


More information about the liberationtech mailing list