From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id E40387EE25 for ; Tue, 19 Nov 2013 23:18:47 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of nicolas.braudsantoni@gmail.com) identity=pra; client-ip=209.85.215.182; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="nicolas.braudsantoni@gmail.com"; x-sender="nicolas.braudsantoni@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of nicolas.braudsantoni@gmail.com designates 209.85.215.182 as permitted sender) identity=mailfrom; client-ip=209.85.215.182; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="nicolas.braudsantoni@gmail.com"; x-sender="nicolas.braudsantoni@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-ea0-f182.google.com) identity=helo; client-ip=209.85.215.182; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="nicolas.braudsantoni@gmail.com"; x-sender="postmaster@mail-ea0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjACAPDii1LRVde2m2dsb2JhbABZw1KBIRYOAQEBAQEGCwsJFCiCJQEBBUABGxwCAwwGBQsNCRYPCQMCAQIBEREBBQEcEwYCAQGHagEDDwQBojWMV4MJhCcKGScNZId2EQEFDI9SFoQcA5AwgTGGMYY/iWJBhFQ X-IPAS-Result: AjACAPDii1LRVde2m2dsb2JhbABZw1KBIRYOAQEBAQEGCwsJFCiCJQEBBUABGxwCAwwGBQsNCRYPCQMCAQIBEREBBQEcEwYCAQGHagEDDwQBojWMV4MJhCcKGScNZId2EQEFDI9SFoQcA5AwgTGGMYY/iWJBhFQ X-IronPort-AV: E=Sophos;i="4.93,732,1378850400"; d="asc'?scan'208";a="43917589" Received: from mail-ea0-f182.google.com ([209.85.215.182]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 19 Nov 2013 23:18:47 +0100 Received: by mail-ea0-f182.google.com with SMTP id o10so4262598eaj.13 for ; Tue, 19 Nov 2013 14:18:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=k+FLf6d6NPQYsVgi1RC2wOCpuFS+/WpG6408KjUqHnM=; b=Hzhvv6ZsI2pW3HiZpHomoaUoTKR17WQPBa76/4eQROdYYjg9yCbA9GnwZf/9vaHBBn 09plop8EzbzN++X3UdK+iSZ5bVo/89PmRh04aF2Ly+YXfSXuUH9Rv9vxGjw1+zDqneW8 RC9HOBAaSQcv5qpfNfVis9g6VE7tW/9UmjkT8pHCCOErpahve+x0srRQwKIJIPKIxomk KgYTXnuFRwb8+YJLwvUSicR3W7p1R5DgpfOCoZ2jqsbidIU60/6lQBU8UqzsgZ0RZUJM p+eCNnEpdLSN0uftbcRHzMEGYSe2rpCDDiZbWtL5eFOmuKQ73eBLSBcQ9NgFako7Lwuy jWsA== X-Received: by 10.15.34.5 with SMTP id d5mr23494010eev.20.1384899527175; Tue, 19 Nov 2013 14:18:47 -0800 (PST) Received: from [193.170.224.192] (m-192.vc-graz.ac.at. [193.170.224.192]) by mx.google.com with ESMTPSA id a51sm53083598eeh.8.2013.11.19.14.18.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Nov 2013 14:18:45 -0800 (PST) Message-ID: <528BE3C3.2050304@gmail.com> Date: Tue, 19 Nov 2013 23:18:43 +0100 From: Nicolas Braud-Santoni User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: caml-list@inria.fr References: <20131118204426.GA14731@annexia.org> <1384819720.4083.57.camel@zotac> <1384859953.62343.YahooMailNeo@web120403.mail.ne1.yahoo.com> <20131119125519.GA18044@ccellier.rd.securactive.lan> In-Reply-To: <20131119125519.GA18044@ccellier.rd.securactive.lan> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wB5a70eK74caoOrwh155HmG3dfMwGcx3Q" Subject: Re: [Caml-list] Hardening [Perl's] hash function further This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wB5a70eK74caoOrwh155HmG3dfMwGcx3Q Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 19/11/2013 13:55, rixed@happyleptic.org wrote: > -[ Tue, Nov 19, 2013 at 03:19:13AM -0800, Dario Teixeira ]---- >> To complicate matters further, on some architectures but not on others >> you may now or in the future have silicon that speeds up the calculation >> of cryptographic hash functions... > To complicate matters even further, many users concerned about security > will refuse to rely on a hardware blackbox implementation anyway. ;-) I am not aware of instruction sets dedicated to speeding up hash functions (unlike encryption with AES, for instance). However, vectorization can definitely help. --wB5a70eK74caoOrwh155HmG3dfMwGcx3Q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJSi+PEAAoJEPv4tP2UoeSeYxgP/jTz5bmGM45DiSlH86iVS6Xp u0fp9SOfMuwsEJ8lw//d4lHC1fkLBmPvteJBFbli+uUImlZWYYQniLIMay7L99z1 SZNhMn+N6xzeDbvyumYxXaR4PAqjO4EAao+yVlIUVrBbdKjFjgd37VneFonIJ2Oc B3ux7+P/ONo69FOtMCCYb7Dm67OifJ4Fco5GxPbYf6oNbg7jjOEFPEDH1Ve00Bns HFhX6ST2ent6TqG1lb3se415ycvjZz7grhXumslQQuBvPvm9Kr4jn/z0+rF3farc ojgjKwpaRpJXvNKIju8dd/eRHaSQTvd4W+fw7g1alryv1mpOM3/LfSi6bC2TdNSy iC3Z91DO+sab3pelvEVgRnC0oisV2pwl+IA3qiNRcCVI95ZR+qHD8lQLw27CJrCT /4bysPMFsSt2fdVkG1ViWXhI7cWPwwMq2ytrMfab40WWc/crUM95Ru/SZwgKEZKO UcfdJ8GMjXMwclvxPCDrutwRev83R1It5q0WN+pbZTgvPO16sM1TRkiCIE6sVNQ0 XH70KWHm96vbIB/nkXjSf4X7kTaYnJbvQyBz1UpLr0MqqgYqSblYFzC15Udk8Xc+ xj2TWXppsA5Rs5Aoh7XJwEAnJCF+tt5mET4AnTNTcxPiTjD6+Y4MUo74cZXkF6hl 6fDHf3+8VyZ+bsUk2nho =6sOj -----END PGP SIGNATURE----- --wB5a70eK74caoOrwh155HmG3dfMwGcx3Q--