BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Crashplan is discontinued
- Subject: [Discuss] Crashplan is discontinued
- From: smallm at sdf.org (Mike Small)
- Date: Fri, 01 Sep 2017 02:02:58 +0000
- In-reply-to: <CAFv2jcZW0fxdYTzvJUehTf9vG=5NA48OHNoDYaFUfYWNuhkFNw@mail.gmail.com> (John Abreau's message of "Thu, 31 Aug 2017 20:36:22 -0400")
- References: <mailman.9.1504195205.26755.discuss@blu.org> <5D31FEA5-F6DC-4F45-BD36-352F588E673E@pioneer.ci.net> <20170831193111.GB12801@newtao.randomstring.org> <CAFv2jcZW0fxdYTzvJUehTf9vG=5NA48OHNoDYaFUfYWNuhkFNw@mail.gmail.com>
John Abreau <abreauj at gmail.com> writes: > I've heard of tools using MD5 or SHA1 hashes to identify duplicates, and > potential issues with hash collisions causing false positives. By accident or maliciously? The numbers seem off for accidental collisions. An md5 sum is a 16 digit hex number. That gives 340282366920938463463374607431768211456 potential hash sums (or does the algorithm offer only a smaller subset?). I'm not going to bother to compute the probability of a collision. It's a very remote possiblity, yes? For the malicious case, if someone's able to mess with the hashes used by deduplication code in your file system or in your hopefully almost as good userland equivalent (which of course must use git in some way or another for reasons that are not clear to me) you have unsolvable problems. I once saw a pointer to a thread speculating about the problem for git (when actually used for source code, go figure), but the hypothetical attack needed a hostile committer. It wasn't an easy attack even then, though that might have been in part from the social engineering challenges of having other committers not notice what you've done. -- Mike Small smallm at sdf.org
- Follow-Ups:
- [Discuss] Crashplan is discontinued
- From: smallm at sdf.org (Mike Small)
- [Discuss] Crashplan is discontinued
- References:
- [Discuss] Crashplan is discontinued
- From: richb at pioneer.ci.net (Rich Braun)
- [Discuss] Crashplan is discontinued
- From: dsr at randomstring.org (Dan Ritter)
- [Discuss] Crashplan is discontinued
- From: abreauj at gmail.com (John Abreau)
- [Discuss] Crashplan is discontinued
- Prev by Date: [Discuss] CrashPlan Home is discontinued - what's next?
- Next by Date: [Discuss] Crashplan is discontinued
- Previous by thread: [Discuss] Crashplan is discontinued
- Next by thread: [Discuss] Crashplan is discontinued
- Index(es):