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
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <timon.elviejo@gmail.com>) id 1SoCEL-0005mt-5A
for bitcoin-development@lists.sourceforge.net;
Mon, 09 Jul 2012 11:34:17 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.47 as permitted sender)
client-ip=209.85.212.47; envelope-from=timon.elviejo@gmail.com;
helo=mail-vb0-f47.google.com;
Received: from mail-vb0-f47.google.com ([209.85.212.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SoCEK-0003SD-3a
for bitcoin-development@lists.sourceforge.net;
Mon, 09 Jul 2012 11:34:17 +0000
Received: by vbbfr13 with SMTP id fr13so7792302vbb.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 09 Jul 2012 04:34:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.21.177 with SMTP id w17mr15755287vde.98.1341833650649; Mon,
09 Jul 2012 04:34:10 -0700 (PDT)
Received: by 10.220.71.78 with HTTP; Mon, 9 Jul 2012 04:34:10 -0700 (PDT)
In-Reply-To: <jtedbo$271$1@dough.gmane.org>
References: <1341825681.35206.YahooMailNeo@web121001.mail.ne1.yahoo.com>
<20120709121949.7hxwomyxskc004w8@webmail.henricson.se>
<1341830670.81383.YahooMailNeo@web121003.mail.ne1.yahoo.com>
<jtedbo$271$1@dough.gmane.org>
Date: Mon, 9 Jul 2012 13:34:10 +0200
Message-ID: <CAGQP0AGG9Wrx0CDQQVwpCovovDV072Cr9rrLhUHuBgb4kNr+XA@mail.gmail.com>
From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= <timon.elviejo@gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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
(timon.elviejo[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: 1SoCEK-0003SD-3a
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Wallet for Android
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: Mon, 09 Jul 2012 11:34:17 -0000
Didn't even know that they were proprietary software bitcoin clients.
Should people trust them? Should the web promote them?
After all, you can't know what they do. What if one of them contains a
back door or something?
I would say it's better not risk to apologize later.
On 7/9/12, Andreas Schildbach <andreas@schildbach.de> wrote:
> I'd suggest adding two links for each client.
>
> One for getting the binary, and one for getting the source. (Obviously,
> source being optional if you allow non-opensource clients.)
>
>
> On 07/09/2012 12:44 PM, Amir Taaki wrote:
>> OK thanks. I just went and made those sections then saw your posts.
>>
>> Anyway we have a section for proprietary clients now. Please tell me if
>> anything looks disagreeable, http://bitcoin.org/clients.html
>>
>> One thing I'm going to do is randomise the positioning order within
>> sections upon refresh.
>>
>>
>>
>> ----- Original Message -----
>> From: "mats@henricson.se" <mats@henricson.se>
>> To: bitcoin-development@lists.sourceforge.net
>> Cc:
>> Sent: Monday, July 9, 2012 11:19 AM
>> Subject: Re: [Bitcoin-development] Bitcoin Wallet for Android
>>
>> Sources are available here:
>>
>> http://code.google.com/p/bitcoin-wallet/
>>
>> Mats
>>
>> Quoting Amir Taaki <zgenjix@yahoo.com>:
>>
>>> Hey,
>>>
>>> I just saw this added to the clients page. One of the conditions we
>>> set for that page was that all the clients must have the entire
>>> sourcecode available for review, and users should be able to run it
>>> from the sourcecode. Is the sourcecode for this client available for
>>> review? I couldn't find it.
>>>
>>> Otherwise, we should make a separate section for non-opensource clients=
.
>>>
>>>
>>> -----------------------------------------------------------------------=
-------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond.
>>> Discussions
>>> will include endpoint security, mobile security and the latest in
>>> malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>
>>
>>
>>
>> ------------------------------------------------------------------------=
------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussion=
s
>>
>> will include endpoint security, mobile security and the latest in malwar=
e
>>
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>> ------------------------------------------------------------------------=
------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussion=
s
>>
>> will include endpoint security, mobile security and the latest in malwar=
e
>>
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>
>
>
>
>
> -------------------------------------------------------------------------=
-----
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--=20
Jorge Tim=F3n
|
