Re: [ftpext] New Version Notification for draft-bryan-ftp-hash-05
Paul Ford-Hutchinson <paulfordh@uk.ibm.com> Mon, 12 July 2010 21:54 UTC
Return-Path: <paulfordh@uk.ibm.com>
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 6A16F3A6878 for <ftpext@core3.amsl.com>; Mon, 12 Jul 2010 14:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 u8ybYtLE2EmK for <ftpext@core3.amsl.com>; Mon, 12 Jul 2010 14:54:44 -0700 (PDT)
Received: from mtagate1.uk.ibm.com (mtagate1.uk.ibm.com [194.196.100.161]) by core3.amsl.com (Postfix) with ESMTP id D247C3A6B63 for <ftpext@ietf.org>; Mon, 12 Jul 2010 14:54:42 -0700 (PDT)
Received: from d06nrmr1707.portsmouth.uk.ibm.com (d06nrmr1707.portsmouth.uk.ibm.com [9.149.39.225]) by mtagate1.uk.ibm.com (8.13.1/8.13.1) with ESMTP id o6CLsn8U005826 for <ftpext@ietf.org>; Mon, 12 Jul 2010 21:54:49 GMT
Received: from d06av06.portsmouth.uk.ibm.com (d06av06.portsmouth.uk.ibm.com [9.149.37.217]) by d06nrmr1707.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o6CLsn041585194 for <ftpext@ietf.org>; Mon, 12 Jul 2010 22:54:49 +0100
Received: from d06av06.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av06.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id o6CLsnpo011821 for <ftpext@ietf.org>; Mon, 12 Jul 2010 15:54:49 -0600
Received: from d06ml069.portsmouth.uk.ibm.com (d06ml069.portsmouth.uk.ibm.com [9.149.38.218]) by d06av06.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id o6CLsnhb011817 for <ftpext@ietf.org>; Mon, 12 Jul 2010 15:54:49 -0600
In-Reply-To: <D2D3FF30-3B2D-4EFA-A308-18A8A56DE596@muada.com>
References: <20100629052221.092623A6A5C@core3.amsl.com> <alpine.DEB.2.00.1006300000470.1493@tvnag.unkk.fr> <AANLkTikZFhGd3PIwDNrNcKymcoRzc4RHxIJU8TGPztTp@mail.gmail.com> <alpine.DEB.2.00.1006291639050.30072@familiar.castaglia.org> <D2D3FF30-3B2D-4EFA-A308-18A8A56DE596@muada.com>
To: ftpext@ietf.org
MIME-Version: 1.0
X-KeepSent: 14A91796:C0BA21B6-8025775E:0076E406; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.0.2FP1 SHF149 July 17, 2009
From: Paul Ford-Hutchinson <paulfordh@uk.ibm.com>
Message-ID: <OF14A91796.C0BA21B6-ON8025775E.0076E406-8025775E.00785E98@uk.ibm.com>
Date: Mon, 12 Jul 2010 23:03:22 +0100
X-MIMETrack: Serialize by Router on D06ML069/06/M/IBM(Release 8.0.2FP2|June 22, 2009) at 12/07/2010 23:03:22, Serialize complete at 12/07/2010 23:03:22
Content-Type: multipart/alternative; boundary="=_alternative 00785AA28025775E_="
Subject: Re: [ftpext] New Version Notification for draft-bryan-ftp-hash-05
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: Mon, 12 Jul 2010 21:54:45 -0000
> Iljitsch van Beijnum wrote on 12/07/2010 10:59:32: > > A more efficient and less DoS-prone way to implement this would be > for the client to tell the server the hash, and for the server to > tell the client whether the file matches the hash. Not sure how this reduces DoS - if a client can STOR/RETR a file then they know the length and 'mini-hash' and thence force the server to repeatedly calculate the full hash. (And if the server is caching the hash, then this isn't a DoS issue in the first place). > > To optimize this, the hash wouldn't be a straigh hash over the > entire file, but consist of three parts: the file length, a hash > over a small part of the file (say, the first and last kilobyte) and > finally a hash over the entire file. So if the length doesn't match, > the file doesn't match the hash and there is no need to access the > file. If the hash over the small part doesn't match, there is no > match and hashing the entire file is avoided. my 2c - this is an unnecessary complication to address a possible threat that can be managed by other mechanisms (throttling HASH requests from a given client, caching the hash, ...) Paul
- Re: [ftpext] New Version Notification for draft-b… Daniel Stenberg
- Re: [ftpext] New Version Notification for draft-b… Anthony Bryan
- Re: [ftpext] New Version Notification for draft-b… TJ Saunders
- Re: [ftpext] New Version Notification for draft-b… Iljitsch van Beijnum
- Re: [ftpext] New Version Notification for draft-b… Paul Ford-Hutchinson
- Re: [ftpext] New Version Notification for draft-b… Anthony Bryan
- Re: [ftpext] New Version Notification for draft-b… Iljitsch van Beijnum
- Re: [ftpext] New Version Notification for draft-b… Anthony Bryan
- Re: [ftpext] New Version Notification for draft-b… Iljitsch van Beijnum
- Re: [ftpext] New Version Notification for draft-b… Richard Koenning
- Re: [ftpext] New Version Notification for draft-b… Tim Kosse