summaryrefslogtreecommitdiff
path: root/35/89c2ed8a1328481a021fd4e4486b40eda5c129
blob: e2c9dd182c1fb82fac2e69456b9dca9763dc0657 (plain)
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
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laszlo@heliacal.net>) id 1WVOIF-00064h-P2
	for bitcoin-development@lists.sourceforge.net;
	Wed, 02 Apr 2014 16:45:39 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of heliacal.net
	designates 91.234.48.203 as permitted sender)
	client-ip=91.234.48.203; envelope-from=laszlo@heliacal.net;
	helo=mail3.heliacal.net; 
Received: from mail3.heliacal.net ([91.234.48.203])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1WVOIE-0000W1-Ia
	for bitcoin-development@lists.sourceforge.net;
	Wed, 02 Apr 2014 16:45:39 +0000
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Laszlo Hanyecz <laszlo@heliacal.net>
In-Reply-To: <533C33E0.9070705@gmail.com>
Date: Wed, 2 Apr 2014 16:45:29 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <916BAE36-90F5-43FF-B05F-71F0BC4B0B00@heliacal.net>
References: <533B1AF4.5010201@gmail.com>	<CAJHLa0OKWZEYh8BjADWukx_gAY9SDX7krW5q97PRkog-Ao+B3w@mail.gmail.com>	<533C2476.20602@gmail.com>	<516CFEDA-5FF8-4367-824A-BDAF5D64E5DA@heliacal.net>	<533C2D04.4090900@gmail.com>
	<CALC81CN3cWa0OjTWueHKxZUDLZpw5n=qLNLxk8QmiSp4QwQyYA@mail.gmail.com>
	<533C33E0.9070705@gmail.com>
To: Kevin <kevinsisco61784@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-Spam-Score: -2.2 (--)
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 SPF_PASS               SPF: sender matches SPF record
	-0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
	-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: 1WVOIE-0000W1-Ia
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Okay, time to bring up bitcoin/bitcoin
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: Wed, 02 Apr 2014 16:45:39 -0000

Maybe he has a fork on the real github.com and the link was a mistake.

http://news.nurse.com/article/20121203/NY02/112030026#.Uzw5UVy2uw8

I think it's possible that 'Kevin' is for real and maybe he doesn't =
realize he linked to a phishing site, if it was an accident.  If this is =
the same person, then he's blind, and maybe that's why he wrote 'U R L' =
instead of the usual 'URL', by using speech to text or some other =
assistive tech.  It might be that he tried to fork =
github.com/bitcoin/bitcoin and just provided the wrong link.  But =
regardless, stay away from the one with two Bs in it.

Thanks,
Laszlo


On Apr 2, 2014, at 3:59 PM, Kevin <kevinsisco61784@gmail.com> wrote:

> On 4/2/2014 11:45 AM, Ricardo Filipe wrote:
>> Kevin,
>> the thing is you gave us a bad link... what is the correct URL of =
your project?
>>=20
>> 2014-04-02 16:30 GMT+01:00 Kevin <kevinsisco61784@gmail.com>:
>>> On 4/2/2014 11:13 AM, Laszlo Hanyecz wrote:
>>>> Maybe this site serves up exploits selectively?  I'm guessing most =
people are getting the 'domain for sale' but whoever is the target =
probably gets something special?
>>>>=20
>>>> On Apr 2, 2014, at 2:53 PM, Kevin <kevinsisco61784@gmail.com> =
wrote:
>>>>=20
>>>>> On 4/2/2014 9:08 AM, Jeff Garzik wrote:
>>>>>> At first, this is a poor choice of URL.
>>>>>>=20
>>>>>> But it really looks like a phishing attempt that no one should =
visit.
>>>>>>=20
>>>>>>=20
>>>>>> On Tue, Apr 1, 2014 at 4:00 PM, Kevin <kevinsisco61784@gmail.com> =
wrote:
>>>>>>> I've sat on this for some time after starting this.  I have =
forked this
>>>>>>> from bitcoin core and am working on a secure tax "mode" for =
bitcoin.  It
>>>>>>> is written in Autoit.  I know I know, scripting language alert!  =
I would
>>>>>>> like people to look at:
>>>>>>> http://www.githubb.com/bitcoin/bitcoin
>>>>>>> Look at it, and let's have an open dialog about it.  I want to =
know the
>>>>>>> good, the bad, and the ugly!
>>>>>>>=20
>>>>>>> --
>>>>>>> Kevin
>>>>>>>=20
>>>>>>>=20
>>>>>>> =
--------------------------------------------------------------------------=
----
>>>>>>> _______________________________________________
>>>>>>> Bitcoin-development mailing list
>>>>>>> Bitcoin-development@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>>> As far as choice of U R L, it may be a poor choice but I did this
>>>>> because I wanted it connected with the core.  As far as fishing it
>>>>> certainly is not that!  This is a serious project.
>>>>>=20
>>>>>=20
>>>>> --
>>>>> Kevin
>>>>>=20
>>>>>=20
>>>>> =
--------------------------------------------------------------------------=
----
>>>>> _______________________________________________
>>>>> Bitcoin-development mailing list
>>>>> Bitcoin-development@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>> I tell you that this is a serious project for bitcoin.  You are free =
to
>>> assume the worst.  After all, I did say the good the bad and the =
ugly
>>> would come out of this.  I happen to be a big believer in bitcoin =
and I
>>> feel this project holds water.  If you disagree, that's fine.
>>>=20
>>>=20
>>> --
>>> Kevin
>>>=20
>>>=20
>>> =
--------------------------------------------------------------------------=
----
>>> _______________________________________________
>>> Bitcoin-development mailing list
>>> Bitcoin-development@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> I understand now why someone thought I was fishing.  That link should =
work just fine...I'm not sure what the problem is as I know I forked =
correctly.  I guess I'll need to register a domain for it an get a page =
going and link from there.  I just haven't gotten around to it but will =
do that.  I'll get going!  Just know that I would never set up fishing; =
that's not my style.
>=20
>=20
> --=20
> Kevin
>=20