public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robin H.Johnson <robbat2@gentoo.org>
To: Fred Van Andel <fava@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] (crazy?) proposal to reduce load and disk on mirrors
Date: Thu, 24 Jul 2003 00:30:30 -0700	[thread overview]
Message-ID: <20030724073030.GD770@cherenkov.orbis-terrarum.net> (raw)
In-Reply-To: <200307222342.26941.fava@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]

On Tue, Jul 22, 2003 at 11:42:26PM -0700, Fred Van Andel wrote:
> As for the security of MD5, there is no published instance of anyone 
> finding 2 different datasets that produce an identical hash value. MD5 
> is a 128 bit hash algorithm so in theory it would be be required to 
> calculate approximately 1.2 * sqrt(2^128) different hashes in order to 
> have a 50% chance of a single collision. That would require > 350 
> billion gigabytes just to store the hashes. I believe MD5 to be secure 
> enough for this application.
I'd be VERY careful with this.
http://www.rsasecurity.com/rsalabs/faq/3-6-6.html

I've seen much more recent research into it myself, along with a way of
making it SIGNIFICENTLY more difficult to break.

Namely, store the correct filesize along with the MD5 sum in a
verifiable fashion. Having file containing a list of tarballs and their
sizes, then providing a GPG signature for that file makes solves the
issue to a level such that even all the computers in the world in 10
years could not beat it [famous last words, after seeing the
crypto-attack on RSA keys using a massive NFS setup].

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2003-07-24  7:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 19:48 [gentoo-dev] The release of 1.4 and its impact on our mirrors Kurt Lieber
2003-07-23  8:40 ` Alvaro Figueroa Cabezas
2003-07-23 21:01   ` Kurt Lieber
2003-07-23  9:28     ` Alvaro Figueroa Cabezas
2003-07-23  9:30       ` Alvaro Figueroa Cabezas
2003-07-24  0:11       ` [gentoo-dev] " Pieter Van den Abeele
2003-07-24  0:55         ` Nathaniel McCallum
2003-07-24  2:07           ` [gentoo-dev] Python on the liveCD Nathaniel McCallum
2003-07-24  9:29             ` Seemant Kulleen
2003-07-23 20:36 ` [gentoo-dev] The release of 1.4 and its impact on our mirrors Matthew Walker
2003-07-23 20:39 ` Tal Peer
2003-07-23 21:10   ` Jon Portnoy
2003-07-23 21:41   ` Alec Berryman
2003-07-24  7:35 ` [gentoo-dev] (crazy?) proposal to reduce load and disk on mirrors Håvard Wall
2003-07-23  5:50   ` Fred Van Andel
     [not found]     ` <3F1F9174.6010504@ifi.uio.no>
2003-07-23  6:04       ` Fred Van Andel
2003-07-24  5:54   ` Raimundo Bilbao
2003-07-23  6:42     ` Fred Van Andel
2003-07-24  7:30       ` Robin H.Johnson [this message]
2003-07-23  7:53         ` Fred Van Andel
2003-07-24  6:35     ` bdharring
2003-07-23  7:22       ` Fred Van Andel
2003-07-24  9:32   ` Mix Sella
2003-07-24 16:39   ` gerrynjr
2003-07-24 15:59     ` Tom Payne

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=20030724073030.GD770@cherenkov.orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=fava@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /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