Re: [ftpext] draft-ietf-ftpext2-hash command name and default algorithm

Daniel Stenberg <daniel@haxx.se> Tue, 18 January 2011 15:58 UTC

Return-Path: <daniel@haxx.se>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28F7D28C1AA for <ftpext@core3.amsl.com>; Tue, 18 Jan 2011 07:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.174
X-Spam-Level:
X-Spam-Status: No, score=-3.174 tagged_above=-999 required=5 tests=[AWL=-0.925, BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JeizKleQI2dt for <ftpext@core3.amsl.com>; Tue, 18 Jan 2011 07:58:39 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by core3.amsl.com (Postfix) with ESMTP id F1EC628C102 for <ftpext@ietf.org>; Tue, 18 Jan 2011 07:58:38 -0800 (PST)
Received: from giant.haxx.se (giant.haxx.se [80.67.6.50]) by giant.haxx.se (8.14.3/8.14.3/Debian-9.1) with ESMTP id p0IG1EQC030449; Tue, 18 Jan 2011 17:01:14 +0100
Date: Tue, 18 Jan 2011 17:01:14 +0100
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Robert Oslin <rto@globalscape.com>
In-Reply-To: <F15941D3C8A2D54D92B341C20CACDF2311979DC5FE@exchange>
Message-ID: <alpine.DEB.2.00.1101181656420.988@tvnag.unkk.fr>
References: <F15941D3C8A2D54D92B341C20CACDF2311976FECC9@exchange> <20110117175600.2F89028C1A2@core3.amsl.com> <F15941D3C8A2D54D92B341C20CACDF2311976FF0A8@exchange> <alpine.DEB.2.00.1101181545230.988@tvnag.unkk.fr> <F15941D3C8A2D54D92B341C20CACDF2311979DC5FE@exchange>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: "ftpext@ietf.org" <ftpext@ietf.org>
Subject: Re: [ftpext] draft-ietf-ftpext2-hash command name and default algorithm
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2011 15:58:40 -0000

On Tue, 18 Jan 2011, Robert Oslin wrote:

>>> I personally think CRC32 is too weak for multi-gigabyte files.
>
> Do you mean that CRC32 is weak period?

CRC32 uses 32 bits to indicate a checksum for the data. I claim it gets weaker 
the more data to try to check with it. Having a CRC32 field for a sufficiently 
small amount of data will be fine IMO - but that's not what we design for 
here.

> One may argue that the "weaker" the hash the faster it will compute, making 
> it ideal for use with larger files (in order to mitigate the chance of 
> client timeouts).

Clients don't have to timeout. The server can easily send "213-" lines every 
5-10 seconds or so while calculating the hash. Or is there a reason why not?

-- 

  / daniel.haxx.se