From owner-freebsd-stable@FreeBSD.ORG Wed Oct 1 02:49:29 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F2E8E45; Wed, 1 Oct 2014 02:49:29 +0000 (UTC) Date: Tue, 30 Sep 2014 22:49:24 -0400 From: Glen Barber To: beeessdee@ruggedinbox.com Subject: Re: svn repo verification (Re: FreeBSD 10.1-BETA3 Now Available) Message-ID: <20141001024924.GX1275@hub.FreeBSD.org> References: <20140928155118.GA75063@hub.FreeBSD.org> <20140929025102.GH75063@hub.FreeBSD.org> <20140929031120.GI75063@hub.FreeBSD.org> <20140929121648.GL75063@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8D1TCnBmjJJF2KCx" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 02:49:30 -0000 --8D1TCnBmjJJF2KCx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 01, 2014 at 04:18:23AM +0200, beeessdee@ruggedinbox.com wrote: > On Mon, September 29, 2014 2:16 pm, "Glen Barber" wrote: > > I don't understand what you mean. We have a verifiable audit trail - it > > is all in svn revision history. >=20 > By this I mean, cryptographic hash chain and signed commits. svn revision > history is audit trail, but not *verifiable* audit trail. >=20 Well, audit trail is why we no longer use CVS. > Is there such things in svn metadata? I did not find. If yes, this > should be Handbook documented (and how to use it). >=20 No, there isn't. > Important because: >=20 > * Data at rest in repository, protected from intrusion or the insider > attack. >=20 Even "insiders" do not have login access directly to svn. > * Data in transit on wire not protected by svn protocol (except for > persons with the ssh access) >=20 svn+https. It is in the Handbook. > * Every person, everywhere should be able confirm downloaded commit > history is exactly equals bit-for-bit what you (gjb@), Core Team, re@ > have in their machines! >=20 I don't quite follow what the core team has to do with this, to be honest... But you can confirm the history. Check out the repository via svn+https =66rom one of the mirrors we say are official. It, too, in the Handbook. > Obscure change (example classic "if(uid=3D=3D0)" to single "if(uid=3D0)")= in > critical piece even 100.000 commits old should be easy detectable by > anyone. >=20 I fail to see the relevance here. > Commit bit should be attached requirement of signing of the commits. >=20 SVN doesn't work that way, and no, I will not entertain the "but $foo VCS does" conversation, which at best, is far outside the scope of a 10.1-BETA announcement email.. Glen --8D1TCnBmjJJF2KCx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUK2u0AAoJEAMUWKVHj+KTTLEP+wYqo99GFHylsaiGzBVihVv9 SpvSfhrLbnXIPibOFsibDWeS5TvgDDCeL/9Kx2b/2bmd+arOAKWYhry+XuSvLiEl osgPjxqkMvtPYDhyj7uDQO5XsUqNOo1fJR8C8EfNEU2GnPODAqpkWoB6Vq5rUpS2 u4mOGe0V5Klntg+bcBCo8oeR7NXfQPxN8mKVcw4/AE9XaTdxcLcGRsXUQwfn/Itf hnm4y1LkKfG/5rwyZoR6p4VlMeH9PE8OkslS71CY91Xo2tZ4buTO6VanCbW9YCf/ CZj9rjaZGB69gzYQq5S2Hm1rCKK+8sRaY8+SRbpCY1JdTnqc+aZAcoWg0tCAylmz +6ZJLsntR47rHfqIyGFbJMTYt45fA9T6bkuQxGHvyxhkTKIJMUGDOkHxECPVfQNj AKgkNME5jBH361s9F1s63IJn09LHUwge975i7+6q1alWa90HTIiUEAWgS0aPVrUw rEYZPv2ET22YLjgCoXbXO8A3MNo4FhkER37eQ83mLZcJTjpZJubcXJQFqEv/9alJ llhKX1VpDG6EVxoyOHopmiVdXW1IDqArhBZHllNnNO9SLuSUbZXq9hlkiPkIDzfD WYqnLTIg6xWL5PaZX6fwJXRVwomfeOtH5f839xm3NSfvFcaAvRcsKIC4YR9FP9QI bxy0VML+RkbMKue2xCrh =4ksk -----END PGP SIGNATURE----- --8D1TCnBmjJJF2KCx--