From: Dmitry Potapov <dpotapov@gmail.com>
To: vinassa vinassa <vinassa.vinassa@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git behaviour question regarding SHA-1 and commits
Date: Mon, 14 Nov 2011 01:14:35 +0300 [thread overview]
Message-ID: <CAHkcothpwYHK7qtmCE-XR8kVKb9bqfbSiWjLPW82SOEhohXR1g@mail.gmail.com> (raw)
In-Reply-To: <CAJuRt+r9BjYcead6hgzdUT0Bisz1D48cegqkoJ0S537VMYBy_g@mail.gmail.com>
On Sun, Nov 13, 2011 at 9:04 PM, vinassa vinassa
<vinassa.vinassa@gmail.com> wrote:
>
> I found some mention of this in the archive, more about SHA-1 security
> implications, that were dismissed, but here I am looking at just a
> random, very unfortunate case, and just wondering if in this case I
> would end up in a FUBAR situation.
I do not see how such an event would be very unfortunate considering
that it would make you instantaneously famous, so you could write a
lot of articles about what happened and make a fortunate of it... but
if we consider a _far_ much more likely event like some object from
the sky falling directly on your head at the moment when you are doing
a commit, that I would be really very unfortunate... So, maybe, you
should rent space in a bunker first just to work safely...
Seriously, it is so ridiculous to worry so much about so improbable
event, while in practice a lot of repository corruptions comes from
unreliable DRAM, disk storage, or some other reasons. The mean time
between failures for high quality components is only a few hundred
years while doing a commit every second will take dozen million
times more than the age of our universe to generate a collision. So,
those probabilities are so different that there is nothing in our
every day experiences that has the same scale difference. It is like
a hair width and the distance to the closest star.
Dmitry
next prev parent reply other threads:[~2011-11-13 22:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 17:04 git behaviour question regarding SHA-1 and commits vinassa vinassa
2011-11-13 17:41 ` Ævar Arnfjörð Bjarmason
2011-11-14 3:29 ` Junio C Hamano
2011-11-14 11:48 ` Jeff King
2011-11-13 18:27 ` Jonathan Nieder
2011-11-13 22:14 ` vinassa vinassa
2011-11-14 11:32 ` Jeff King
2011-11-14 12:48 ` Victor Engmark
2011-11-14 13:04 ` Jeff King
2011-11-13 22:14 ` Dmitry Potapov [this message]
2011-11-14 7:39 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHkcothpwYHK7qtmCE-XR8kVKb9bqfbSiWjLPW82SOEhohXR1g@mail.gmail.com \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=vinassa.vinassa@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).