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
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <alonmuroch@gmail.com>) id 1Whadr-0001LZ-GB
for bitcoin-development@lists.sourceforge.net;
Tue, 06 May 2014 08:22:23 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.177 as permitted sender)
client-ip=74.125.82.177; envelope-from=alonmuroch@gmail.com;
helo=mail-we0-f177.google.com;
Received: from mail-we0-f177.google.com ([74.125.82.177])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Whadp-00074d-VY
for bitcoin-development@lists.sourceforge.net;
Tue, 06 May 2014 08:22:23 +0000
Received: by mail-we0-f177.google.com with SMTP id x48so3232215wes.22
for <bitcoin-development@lists.sourceforge.net>;
Tue, 06 May 2014 01:22:15 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.92.228 with SMTP id cp4mr75126wjb.81.1399364535771; Tue,
06 May 2014 01:22:15 -0700 (PDT)
Received: by 10.194.109.100 with HTTP; Tue, 6 May 2014 01:22:15 -0700 (PDT)
In-Reply-To: <70790f686997e51d680e9bde0c9d5a3e.squirrel@fulvetta.riseup.net>
References: <le05ca$qn5$1@ger.gmane.org> <5303B110.70603@bitpay.com>
<le0jvf$i7d$1@ger.gmane.org>
<CAJHLa0MGaxJTGPR-bduW36-4Msb348FANqFmw67jqFxq1CLwbw@mail.gmail.com>
<70790f686997e51d680e9bde0c9d5a3e.squirrel@fulvetta.riseup.net>
Date: Tue, 6 May 2014 10:22:15 +0200
Message-ID: <CADCNpyO49OvysOB3RBEY1D8ei6Oz2xrd=ifmzC_3cbz1Wu09rQ@mail.gmail.com>
From: Alon Muroch <alonmuroch@gmail.com>
To: Odinn Cyberguerrilla <odinn.cyberguerrilla@riseup.net>
Content-Type: multipart/alternative; boundary=047d7bfd0bde10e70d04f8b6f265
X-Spam-Score: -0.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
(alonmuroch[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Whadp-00074d-VY
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] BIP70 proposed changes
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: Tue, 06 May 2014 08:22:23 -0000
--047d7bfd0bde10e70d04f8b6f265
Content-Type: text/plain; charset=UTF-8
Hi Odinn,
There is a tromendous progress and we are working hard on the 2 factor
auth.
You an follow our progress at :
https://github.com/cpacia/BitcoinAuthenticator
We are still at development and there is a lot to be done :)
On Tue, May 6, 2014 at 4:35 AM, Odinn Cyberguerrilla <
odinn.cyberguerrilla@riseup.net> wrote:
> I am curious if the Android developer who had been working on two factor
> authentication and bitcoin had worked toward an open issue or pull
> request? I had been looking around for some sign that this had occurred
> but hadn't found it, I am interested to know what is the progress in this
> area (in a fully decentralized way that resides fully on one's device or
> devices).
>
> For some reason maidsafe keeps rising up in my brain, have bitcoin core
> developers touched bases with maidsafe developers on these kind of fine
> points?
>
> Just thoughts and questions.
>
> -Odinn
>
> > On Tue, Feb 18, 2014 at 4:40 PM, Andreas Schildbach
> > <andreas@schildbach.de> wrote:
> >> On 02/18/2014 08:14 PM, Ryan X. Charles wrote:
> >>> BitPay is working on a new standard
> >>> based on bitcoin-like addresses for authentication. It would be great
> >>> if
> >>> we could work with the community to establish a complete, decentralized
> >>> authentication protocol.
> >>
> >> Sounds interesting, let us know as soon as you have anything.
> >
> > SINs. See https://en.bitcoin.it/wiki/Identity_protocol_v1
> >
> > --
> > Jeff Garzik
> > Bitcoin core developer and open source evangelist
> > BitPay, Inc. https://bitpay.com/
> >
> >
> ------------------------------------------------------------------------------
> > Managing the Performance of Cloud-Based Applications
> > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> > Read the Whitepaper.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
>
>
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7bfd0bde10e70d04f8b6f265
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi=C2=A0<span style=3D"font-family:arial,sans-serif;font-s=
ize:13px;font-weight:bold;white-space:nowrap">Odinn,</span><div>There is a =
tromendous progress and we are working hard on the 2 factor auth.=C2=A0</di=
v><div>You an follow our progress at :</div>
<div><a href=3D"https://github.com/cpacia/BitcoinAuthenticator">https://git=
hub.com/cpacia/BitcoinAuthenticator</a></div><div><br></div><div>We are sti=
ll at development and there is a lot to be done :)=C2=A0</div></div><div cl=
ass=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Tue, May 6, 2014 at 4:35 AM, Odinn Cy=
berguerrilla <span dir=3D"ltr"><<a href=3D"mailto:odinn.cyberguerrilla@r=
iseup.net" target=3D"_blank">odinn.cyberguerrilla@riseup.net</a>></span>=
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I am curious if the Android developer who ha=
d been working on two factor<br>
authentication and bitcoin had worked toward an open issue or pull<br>
request? =C2=A0I had been looking around for some sign that this had occurr=
ed<br>
but hadn't found it, I am interested to know what is the progress in th=
is<br>
area (in a fully decentralized way that resides fully on one's device o=
r<br>
devices).<br>
<br>
For some reason maidsafe keeps rising up in my brain, have bitcoin core<br>
developers touched bases with maidsafe developers on these kind of fine<br>
points?<br>
<br>
Just thoughts and questions.<br>
<br>
-Odinn<br>
<br>
> On Tue, Feb 18, 2014 at 4:40 PM, Andreas Schildbach<br>
> <<a href=3D"mailto:andreas@schildbach.de">andreas@schildbach.de</a>=
> wrote:<br>
>> On 02/18/2014 08:14 PM, Ryan X. Charles wrote:<br>
>>> BitPay is working on a new standard<br>
>>> based on bitcoin-like addresses for authentication. It would b=
e great<br>
>>> if<br>
>>> we could work with the community to establish a complete, dece=
ntralized<br>
>>> authentication protocol.<br>
>><br>
>> Sounds interesting, let us know as soon as you have anything.<br>
><br>
> SINs. =C2=A0See <a href=3D"https://en.bitcoin.it/wiki/Identity_protoco=
l_v1" target=3D"_blank">https://en.bitcoin.it/wiki/Identity_protocol_v1</a>=
<br>
><br>
> --<br>
> Jeff Garzik<br>
> Bitcoin core developer and open source evangelist<br>
> BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" targe=
t=3D"_blank">https://bitpay.com/</a><br>
><br>
> ----------------------------------------------------------------------=
--------<br>
> Managing the Performance of Cloud-Based Applications<br>
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.=
<br>
> Read the Whitepaper.<br>
> <a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D121054471&a=
mp;iu=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.ne=
t/gampad/clk?id=3D121054471&iu=3D/4140/ostg.clktrk</a><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
><br>
<br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
Is your legacy SCM system holding you back? Join Perforce May 7 to find out=
:<br>
&#149; 3 signs your SCM is hindering your productivity<br>
&#149; Requirements for releasing software faster<br>
&#149; Expert tips and advice for migrating your SCM now<br>
<a href=3D"http://p.sf.net/sfu/perforce" target=3D"_blank">http://p.sf.net/=
sfu/perforce</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>
--047d7bfd0bde10e70d04f8b6f265--
|
