From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1VceR2-000408-6c for bitcoin-development@lists.sourceforge.net; Sat, 02 Nov 2013 16:52:28 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.49 as permitted sender) client-ip=209.85.215.49; envelope-from=melvincarvalho@gmail.com; helo=mail-la0-f49.google.com; Received: from mail-la0-f49.google.com ([209.85.215.49]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VceR0-0007ul-Tg for bitcoin-development@lists.sourceforge.net; Sat, 02 Nov 2013 16:52:28 +0000 Received: by mail-la0-f49.google.com with SMTP id ev20so2511757lab.22 for ; Sat, 02 Nov 2013 09:52:20 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.171.228 with SMTP id ax4mr5065136lbc.6.1383411140168; Sat, 02 Nov 2013 09:52:20 -0700 (PDT) Received: by 10.112.159.233 with HTTP; Sat, 2 Nov 2013 09:52:20 -0700 (PDT) In-Reply-To: References: <20131102050144.5850@gmx.com> <5274FBF7.90301@iki.fi> Date: Sat, 2 Nov 2013 17:52:20 +0100 Message-ID: From: Melvin Carvalho To: Mike Hearn Content-Type: multipart/alternative; boundary=001a11c3704496945504ea348195 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: doubleclick.net] -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 (melvincarvalho[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: 1VceR0-0007ul-Tg Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Message Signing based authentication X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Nov 2013 16:52:28 -0000 --001a11c3704496945504ea348195 Content-Type: text/plain; charset=ISO-8859-1 On 2 November 2013 17:26, Mike Hearn wrote: > Guys, identity systems for the web are off-topic for this list. Other than > the anonymous passports/SINs/fidelity bond ideas, Bitcoin doesn't have any > relevance to it. > > On Sat, Nov 2, 2013 at 2:19 PM, Hannu Kotipalo wrote: > >> Maybe this is a bit off-topic, but the *real* answer to the question >> "why-is-nobody-using-ssl-client-certificates" is that it would force >> www pages to be encrypted and would make it a lot more difficult for >> NSA to log www-trafic. >> > > No, it wouldn't. You can log a user in using SSL and then redirect the > user back to an encrypted page, using cookies for the rest of the session. > Please don't clutter up this list with conspiracy theories. The brutal > reality is that identity is a hard problem. > Identity need not be a hard problem. In my view it is a solved problem. You have a real world entity translated to a digital format. Yes that can be slightly ambiguous at time, naming is hard, and people do get this wrong frequently. The most common problem is to name something in a way that does not scale. The solution to this problem is rather easy, and that is to use a URI to name something, which makes it global and scalable. In the case of bitcoin you could have use the bitcion URI scheme bitcion:1fhdjkfhjksf... > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --001a11c3704496945504ea348195 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 2 November 2013 17:26, Mike Hearn <mike@plan99.net> wrote:


-----------------------------------------------------------------------= -------
Android is increasing in popularity, but the open development platform that=
developers love is also attractive to malware creators. Download this white=
paper to learn more about secure code signing practices that can help keep<= br> Android apps secure.
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D65839951&iu=3D/4140/ostg.clktrk
___________________= ____________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--001a11c3704496945504ea348195--