Re: [Hipsec] How much for that hash?
Andrew McGregor <andrewmcgr@gmail.com> Wed, 09 June 2010 06:56 UTC
Return-Path: <andrewmcgr@gmail.com>
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 5CA6F3A68EB for <hipsec@core3.amsl.com>; Tue, 8 Jun 2010 23:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level:
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
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 0YIz9JPDi1oY for <hipsec@core3.amsl.com>; Tue, 8 Jun 2010 23:56:49 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 5584C3A6868 for <hipsec@ietf.org>; Tue, 8 Jun 2010 23:56:49 -0700 (PDT)
Received: by pwi8 with SMTP id 8so2732964pwi.31 for <hipsec@ietf.org>; Tue, 08 Jun 2010 23:56:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=g6YwkbLhCZxSsMxWiPCwgbBq9SLrNImSSFYy0K5oKpo=; b=liAe48v6qVsUkOfheiuqsvfl/gTtkSWvjaOyIP/5Xy+tyQG+cGK/1v42Qv5ZReE//a Lunw8ICkVKsd8YJD01LYS8+WWnwzLjhBBGZyekxJO46RTQjnOp1vDZd7cMkjth9ezDf1 N/L7Yr/g63u4PhilaXgQ3wIr5EePaEJbVU7qA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=w8xvfWYe+kANZjEZ5qIVyR9Y/pPiV7RQrGQGzKO8ebj25xm0JGT9I4G3jYfcYBa+8m mLLxWsGDJ9PIf89yYocPA+jekqQqhxCpKR7C0p/Vbn8TyqbTOtO6CQ18bFbNBkvDZKvP eJYb9bJnEaOsHxE1FUDI3cCxMStq8FB+1u0PI=
Received: by 10.115.64.20 with SMTP id r20mr13879721wak.205.1276066607986; Tue, 08 Jun 2010 23:56:47 -0700 (PDT)
Received: from [192.168.1.100] (121-72-135-117.dsl.telstraclear.net [121.72.135.117]) by mx.google.com with ESMTPS id d20sm60516991waa.3.2010.06.08.23.56.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 08 Jun 2010 23:56:46 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Andrew McGregor <andrewmcgr@gmail.com>
In-Reply-To: <4C0F31CA.6040101@cs.hut.fi>
Date: Wed, 09 Jun 2010 18:56:40 +1200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9B3EBCC-4FA3-4DCA-9596-1EDE1EEF3616@indranet.co.nz>
References: <4C0E9CBD.20600@htt-consult.com> <4C0F31CA.6040101@cs.hut.fi>
To: Miika Komu <mkomu@cs.hut.fi>
X-Mailer: Apple Mail (2.1078)
X-Mailman-Approved-At: Wed, 16 Jun 2010 23:41:20 -0700
Cc: hipsec@ietf.org
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:56:51 -0000
There's a big table of sizes of different crypto algorithms with many different optimisations here: http://www.das-labor.org/wiki/AVR-Crypto-Lib/en The target processor is AVR, commonly used for these embedded systems. Andrew On 09/06/2010, at 6:16 PM, Miika Komu wrote: > 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). > _______________________________________________ > Hipsec mailing list > Hipsec@ietf.org > https://www.ietf.org/mailman/listinfo/hipsec >
- [Hipsec] How much for that hash? Robert Moskowitz
- Re: [Hipsec] How much for that hash? Miika Komu
- Re: [Hipsec] How much for that hash? Andrew McGregor
- [Hipsec] How much for that hash? Tero Kivinen