Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YGVaq-00079y-MG for bitcoin-development@lists.sourceforge.net; Wed, 28 Jan 2015 16:35:52 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitonic.nl designates 178.22.57.41 as permitted sender) client-ip=178.22.57.41; envelope-from=giuseppe@bitonic.nl; helo=mail.entix.nl; Received: from mail.entix.nl ([178.22.57.41]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1YGVan-00010O-Jb for bitcoin-development@lists.sourceforge.net; Wed, 28 Jan 2015 16:35:52 +0000 Message-ID: <54C90C2B.3090708@bitonic.nl> Date: Wed, 28 Jan 2015 17:19:55 +0100 From: Giuseppe Mazzotta User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1YGVan-00010O-Jb Subject: Re: [Bitcoin-development] BIP70: why Google Protocol Buffers for encoding? 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: Wed, 28 Jan 2015 16:35:52 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 28-01-15 16:42, Mike Hearn wrote: > Just as a reminder, there is no obligation to use the OS root > store. You can (and quite possibly should) take a snapshot of the=20 > Mozilla/Apple/MSFT etc stores and load it in your app. We do this > in bitcoinj by default to avoid cases where BIP70 requests work on > some platforms and not others, although the developer can easily > override this and use the OS root store instead. >=20 Except that Mozilla/Apple/MSFT will update these certificate stores - second their policies - and your snapshot/collection might get outdated at a different pace than the OS-provided certificates, depending on how you (or the package maintainer) are rolling out updates. I am not saying that OS-provided certificate stores are a holy grail, as they comes with their quirks&headaches (for example try to install your CA certificate on Mac), but generally I consider shipping your own snapshot a bad practice, as it makes the system less secure by default for the casual user and harder to audit for the (eventual) admins= . If you are a developer, that's a whole different story. - --=20 Giuseppe Mazzotta /- Bitonic _/ -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJUyQwrAAoJEKWX1kB3NXekfLkH/3Bd2yPD0ccZRUzWJ47wQmFd uRxpOjlxZMy3ww4PpxPxqJTrSwyH0gwbNCbuXkds9kkx9+AwxEkT8VZXZVA1KNeo RaLNgqs4R5zK06shTjV+AXe5HwDCEeFuJIIRGM35D8kSKtbPuzKe5UtiIRaBRdZG e+d6CQKklYK8yn24hUGg30Y0rEcrLicXmcJlrjElA+8pKYDIeP3SrMWjLj9QKFhJ VBKxXlyviZ2LGf9wD6p+GLgjDu4LNEQdJPpTNzg7yWSegnKmxopefojkCrHtqJQ7 LC4Lr3K3hp5Nbct1YWRt09VQYic/xaGBCSUdKTEL1xTUv7oD/DY7l15zjKi7gtw=3D =3DZJVu -----END PGP SIGNATURE-----