Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1Vce22-0001DF-JE
	for bitcoin-development@lists.sourceforge.net;
	Sat, 02 Nov 2013 16:26:38 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.176 as permitted sender)
	client-ip=209.85.214.176; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f176.google.com; 
Received: from mail-ob0-f176.google.com ([209.85.214.176])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Vce21-0004EO-Qt
	for bitcoin-development@lists.sourceforge.net;
	Sat, 02 Nov 2013 16:26:38 +0000
Received: by mail-ob0-f176.google.com with SMTP id uy5so5712657obc.35
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 02 Nov 2013 09:26:32 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.230.197 with SMTP id ta5mr6944385oec.16.1383409592467;
	Sat, 02 Nov 2013 09:26:32 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.156.42 with HTTP; Sat, 2 Nov 2013 09:26:32 -0700 (PDT)
In-Reply-To: <CANEZrP2N1DRBcN4JuXKJAodKwk=qNk5hiSnLyx1vbQ1gAd=EhQ@mail.gmail.com>
References: <20131102050144.5850@gmx.com>
	<CANEZrP2UwEX+u0XCxmaMaRWqVMr+3E63UYnVz9oMubbsiJU+6A@mail.gmail.com>
	<5274FBF7.90301@iki.fi>
	<CANEZrP2N1DRBcN4JuXKJAodKwk=qNk5hiSnLyx1vbQ1gAd=EhQ@mail.gmail.com>
Date: Sat, 2 Nov 2013 17:26:32 +0100
X-Google-Sender-Auth: wLp032Cf5EBI4V1plFwAidxIIbg
Message-ID: <CANEZrP2=JBEA72KeK0-5qHm855P8sB1=-NrJugXw6OEA9VxCkQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Hannu Kotipalo <hannu.kotipalo@iki.fi>
Content-Type: multipart/alternative; boundary=001a11363f9e5689cf04ea342591
X-Spam-Score: -0.5 (/)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1Vce21-0004EO-Qt
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <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, 02 Nov 2013 16:26:38 -0000

--001a11363f9e5689cf04ea342591
Content-Type: text/plain; charset=UTF-8

> No, it wouldn't. You can log a user in using SSL and then redirect the
user back to an encrypted page

sorry, I meant unencrypted page of course

--001a11363f9e5689cf04ea342591
Content-Type: text/html; charset=UTF-8

<div dir="ltr">&gt; No, it wouldn&#39;t. You can log a user in using SSL and then redirect the user back to an encrypted page<div><br></div><div>sorry, I meant unencrypted page of course</div></div>

--001a11363f9e5689cf04ea342591--