From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Rcbef-0008Dk-36 for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 11:45:17 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=andyparkins@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RcbeZ-000082-Ne for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 11:45:17 +0000 Received: by werm13 with SMTP id m13so1826503wer.34 for ; Mon, 19 Dec 2011 03:45:05 -0800 (PST) Received: by 10.216.139.140 with SMTP id c12mr6799180wej.26.1324295105587; Mon, 19 Dec 2011 03:45:05 -0800 (PST) Received: from dvr.localnet (mail.360visiontechnology.com. [92.42.121.178]) by mx.google.com with ESMTPS id fw16sm25360246wbb.13.2011.12.19.03.45.03 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 19 Dec 2011 03:45:03 -0800 (PST) From: Andy Parkins To: bitcoin-development@lists.sourceforge.net Date: Mon, 19 Dec 2011 11:44:59 +0000 User-Agent: KMail/1.13.6 (Linux/3.0.0-1-686-pae; KDE/4.6.3; i686; ; ) References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8385282.5JSCYqT214"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201112191145.02427.andyparkins@gmail.com> 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 (andyparkins[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 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RcbeZ-000082-Ne Subject: Re: [Bitcoin-development] [BIP 15] Aliases 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: Mon, 19 Dec 2011 11:45:17 -0000 --nextPart8385282.5JSCYqT214 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On 2011 December 19 Monday, Jorge Tim=F3n wrote: > Ok, so HTTP is not an option unless it shows a huge warning. I don't > know the HTTPS possible attack, but maybe it needs a warning message > too, from what you people are saying. Although using namecoin to The problems with HTTPS have been social rather than technical. Multiple C= As=20 have been strong-armed by governments or tricked into issuing fake=20 certificates by scammers. There is no technical measure around that. By=20 using the CA certificate we are saying to the system "here is someone I tru= st=20 to issue a certificate". So far, with a large number of CAs, that trust is= =20 misplaced. I'm of the opinion though that this problem is outside the remit of bitcoin= to=20 solve. Perhaps we should be more strict about which CA certificates are trusted by= =20 the bitcoin client: say restrict it to those who have demonstrably good=20 practices for verifying identity; rather than the ridiculous amount of trus= t=20 that comes pre-installed for me in my browser. Andy =2D-=20 Dr Andy Parkins andyparkins@gmail.com --nextPart8385282.5JSCYqT214 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk7vI7sACgkQwQJ9gE9xL2318ACeK/RL1lKs82WfPTWyzL56JN/B GJMAoMWtM8c11VRMxcvREPntD+M/LwDt =uaQt -----END PGP SIGNATURE----- --nextPart8385282.5JSCYqT214--