From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 18 14:09:53 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4B69E4EB; Sun, 18 Nov 2012 14:09:53 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id D58BA8FC14; Sun, 18 Nov 2012 14:09:52 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so5224619oag.13 for ; Sun, 18 Nov 2012 06:09:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Fxd0GDXvVqbvoBdexDpqOq/WVHiHJj1QHVU0ONX9X2g=; b=FGN/K3naDwhbszqyXFOhJnH3N4dYHaH/d33bISUpCAvcj/Jc0NSgSm8BH3LLHxpXIi GdmZ+y0EZvvHL85lGG2N9DqV1rg2q5JcLqE1TprYDFOmKx74EaIo8uMSS6xsmgc+1xRm KBf8zC5nzizw3RCzKUXinWX9cxZ++QEaVivgkrFdLdPAcvtQ8Y0nG/L8L7MPty4iGi+H y7lKsenmhfO9m91tjr2cRvciBPsjXahtyrY4O4DY2GTuezKYzd9GF7QpclxXc52ZMNPH sJhzUpTFNcWc1HWK1BS1fJzUHYnn4yM+xebzgZAh7Xnnm0YMn+8qTJ9iP+8r9tpT0BJS kszQ== MIME-Version: 1.0 Received: by 10.60.171.134 with SMTP id au6mr8294960oec.69.1353247792245; Sun, 18 Nov 2012 06:09:52 -0800 (PST) Received: by 10.60.132.50 with HTTP; Sun, 18 Nov 2012 06:09:52 -0800 (PST) Received: by 10.60.132.50 with HTTP; Sun, 18 Nov 2012 06:09:52 -0800 (PST) In-Reply-To: <50A8BD0F.7030609@FreeBSD.org> References: <20121117221143.41c29ba2@nonamehost> <50a8eb34.5pMwq6kSsi47QgKI%perryh@pluto.rain.com> <20121118073128.GG73505@kib.kiev.ua> <50A8BD0F.7030609@FreeBSD.org> Date: Sun, 18 Nov 2012 16:09:52 +0200 Message-ID: Subject: Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident] From: Alexander Yerenkow To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Konstantin Belousov , freebsd-hackers@freebsd.org, Adrian Chadd , Perry Hutchison X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 14:09:53 -0000 Integrity could be provided by storing some kind of commit ( each, and additionally each 1000nd full) checksums (even for svn) somewhere on readonly format. How about each commit will make a "tweet"? I'm sure twitter could arrange create-records-only (no edit) acount for such project as FreeBSD is. This isn't so hard to make, and it's so social :) Regards, Alexander Yerenkow