linux-kernel - Re: [ANNOUNCE] GIT 1.6.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:  <slrngl8dc8.klo.sitaramc@sitaramc.homelinux.net>
Date:	Fri, 26 Dec 2008 01:38:16 +0000 (UTC)
From:	Sitaram Chamarty <sitaramc@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	git@...r.kernel.org
Subject:  Re: [ANNOUNCE] GIT 1.6.1

["Followup-To:" header set to gmane.comp.version-control.git.]
On 2008-12-25, Heikki Orsila <shdl@...alwe.fi> wrote:
> * What would be the probability for a single bit flip to corrupt the 
> repository?

> * And what is the situation where a single bit flip can not corrupt the 
> database?

These two questions are not specific to git; whatever
answers apply to sha1 also apply here.  Sha1 will always be
strong enough to detect any combination of random errors.
As for deliberate attacks, it is considered strong enough to
resist all but the most computationally intensive attacks
(the kind that require a worldwide effort or maybe NSA type
facilities).

> * When (which commands/functions) is error detection done?

"git fsck --full" will do it of course, but I'm not sure
what other operations also start off or end up doing a
check.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/