IETF Logo Mail Archive

Re: [babel] Some open HMAC issues

Dave Taht <dave.taht@gmail.com> Mon, 02 July 2018 16:39 UTC

Return-Path: <dave.taht@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E86A7130ECA for <babel@ietfa.amsl.com>; Mon, 2 Jul 2018 09:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UzS1FPCoUqLB for <babel@ietfa.amsl.com>; Mon, 2 Jul 2018 09:39:36 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4999C130DC6 for <babel@ietf.org>; Mon, 2 Jul 2018 09:39:36 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id c5-v6so14310482qth.5 for <babel@ietf.org>; Mon, 02 Jul 2018 09:39:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eAOrU46KKKjonEv3smVeT2MBIH0ufl6t5OnX3OUA/DI=; b=jQaZ/5vx0iA8ymkvHcH4CK2b1sXPCVGzZmb31VF1Sbca6MrrgKWt7lPAScqcLuSXmX gvNRmfo5zrBhbVhct49K3tNTuyr4xBOQ2RG6vE96BLjJYJNwuZS8KVkx6ege9zHRigug bhn1LpMy1POva/7chm20dGm2rWviIzbth81eG5FsWZ09hVpaQ/CLUeZReT6W6bolHlAT xL0tCFaAxqjQ4oys8SL5zoZmD4jWMRZZYvMDVswDf8rChK8BNuIVXLNK4oQvhIfwcb+8 4JunA3wBNa1QStkf9qJX09F8Iposzh4CVNsXwFFPTUjWT/JdpOqP4Z/5B/gOd5F80dta qYQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eAOrU46KKKjonEv3smVeT2MBIH0ufl6t5OnX3OUA/DI=; b=pvRkblsjVGFu7brs1aKVHumNBQIf7n5zfUklxMkGWGQASJdnvOSEMvXx3fkh8DW8sq Qgs3ha1Hb/1ow3MWRKQ0eD/FOxt0+9QYTprwQUFJgjkh9rDWC756fMEAH4mE8/a8qngO nDVbVLRFvtmSfU74EtcaNDXwIdhc2odAvXdm4XZGwaMzM6wgTqZnp0M5xR9E5Q2AIgXF kdTJO79XTUO0Ct87PepslNtDT366nBJvzj23Irx5vwqon63oN+YwTRAOIyi0RGXxkwIP Dxdm0C3iX8rK4wJbmVe+ei37dHA7tMgngReuOQZKq5jeJHPl4mOFWdfsZ0E4BSbAh91H EkDQ==
X-Gm-Message-State: APt69E1L3FJMF0jClgXBF2OWfuB923hDZER+6OPBq9G2iGzZM2oOEead bLTeXbaTGaMJ4TGJtUmPXiiH8u/qbCjoTi22x8Y=
X-Google-Smtp-Source: AAOMgpeggUHZq5onzb0a4nmCcsDoHkgAhyDAihSsN3JIMiCvXNeSMMRqigsGj7VdbAAgTO0qi5Y+Pr8bDXar1rSbkFw=
X-Received: by 2002:ac8:683:: with SMTP id f3-v6mr24559542qth.104.1530549575378; Mon, 02 Jul 2018 09:39:35 -0700 (PDT)
MIME-Version: 1.0
References: <87sh545st3.wl-jch@irif.fr> <411E2C9F-A910-4899-8DD7-92C0C85EBC54@apple.com> <87tvpihr6g.fsf@toke.dk>
In-Reply-To: <87tvpihr6g.fsf@toke.dk>
From: Dave Taht <dave.taht@gmail.com>
Date: Mon, 02 Jul 2018 09:39:22 -0700
Message-ID: <CAA93jw55uY6cE_EnsMSiZHD=PyZAhigMB5o4eBByApDOjngekw@mail.gmail.com>
To: Toke Høiland-Jørgensen <toke@toke.dk>
Cc: David Schinazi <dschinazi@apple.com>, Juliusz Chroboczek <jch@irif.fr>, weronika.kolodziejak@gmail.com, clarado_perso@yahoo.fr, Babel at IETF <babel@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/JExlSU725favD0ZYCQ8uzy4K0Ko>
Subject: Re: [babel] Some open HMAC issues
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2018 16:39:38 -0000

Defeating SHA1 to my knowledge requires a ridiculous amount of data to obtain
a collision. when the total amount of data you are covering ranges
from 64-1500 bytes, I don't see a problem.

(totally not a crypto expert here, however)

v2.23.0 | Report a Bug | By Email