1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1TPUV5-00051b-BC
for bitcoin-development@lists.sourceforge.net;
Sat, 20 Oct 2012 08:33:43 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.47 as permitted sender)
client-ip=209.85.215.47; envelope-from=laanwj@gmail.com;
helo=mail-la0-f47.google.com;
Received: from mail-la0-f47.google.com ([209.85.215.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TPUV4-0000Ve-Jz
for bitcoin-development@lists.sourceforge.net;
Sat, 20 Oct 2012 08:33:43 +0000
Received: by mail-la0-f47.google.com with SMTP id h5so741569lam.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 20 Oct 2012 01:33:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.44.65 with SMTP id c1mr29127lbm.62.1350722015873; Sat, 20
Oct 2012 01:33:35 -0700 (PDT)
Received: by 10.112.43.138 with HTTP; Sat, 20 Oct 2012 01:33:35 -0700 (PDT)
In-Reply-To: <5082561E.4030907@yahoo.com>
References: <5082561E.4030907@yahoo.com>
Date: Sat, 20 Oct 2012 10:33:35 +0200
Message-ID: <CA+s+GJDBEkYrZ5izTOkGwxytKH4Vb=v4XgHBE2bg62G740Y+9Q@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Mark Lister <mark.lister@yahoo.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1TPUV4-0000Ve-Jz
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Hosting of compiled bitcoin client
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 20 Oct 2012 08:33:43 -0000
On Sat, Oct 20, 2012 at 9:43 AM, Mark Lister <mark.lister@yahoo.com> wrote:
>>The issue is not cryptography, it's "trade with sanctioned countries",
> period, where making
>>files available to download is considered trade.
>
> Spot on, in 2005 when I lived in (among other places) Sudan, Sourceforge
> would block certain downloads (but not the project site). That said it
> was trivial to bypass the restrictions then.
I don't think it's related to these sanctions but to the Great
Firewall of China, but sourceforge downloads are also blocked in
China. Also quite easy to bypass though.
Wladimir
|
