Re: [Hipsec] How much for that hash?

Miika Komu <mkomu@cs.hut.fi> Wed, 09 June 2010 06:14 UTC

Return-Path: <mkomu@cs.hut.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C3BB63A68F1 for <hipsec@core3.amsl.com>; Tue, 8 Jun 2010 23:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level:
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_50=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 ML+NPJEC-1G2 for <hipsec@core3.amsl.com>; Tue, 8 Jun 2010 23:14:10 -0700 (PDT)
Received: from hutcs.cs.hut.fi (hutcs.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id 2D1C33A68F0 for <hipsec@ietf.org>; Tue, 8 Jun 2010 23:14:09 -0700 (PDT)
Received: from hutcs.cs.hut.fi ([130.233.192.7] helo=[127.0.0.1]) by hutcs.cs.hut.fi with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54) id 1OMEYC-0000Y5-Iu for hipsec@ietf.org; Wed, 09 Jun 2010 09:14:08 +0300
Message-ID: <4C0F31CA.6040101@cs.hut.fi>
Date: Wed, 09 Jun 2010 09:16:42 +0300
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11pre) Gecko/20100531 Shredder/3.0.6pre
MIME-Version: 1.0
To: hipsec@ietf.org
References: <4C0E9CBD.20600@htt-consult.com>
In-Reply-To: <4C0E9CBD.20600@htt-consult.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] How much for that hash?
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 06:14:17 -0000

On 08/06/10 22:40, Robert Moskowitz wrote:

Hi,

> It is really being driven home to me how important a cryptographic hash
> is to a total security solution. Trying to design around this is really
> hard!
>
> So since the argument for not using a hash is the code cost, can anyone
> supply me with a good value for the amount of code (in Kb) for SHA-1?
> For SHA-256?

good point. I am not sure if this was a rhetorical question but replying 
nevertheless :) For example, the the SHA1 code in RFC4634 consists of 
total 700 hundreds lines of code, including the header file, or 332 
physical lines of code (sloccount).