Re: [hybi] frame length encoding

"Shelby Moore" <shelby@coolpage.com> Sun, 22 August 2010 23:52 UTC

Return-Path: <shelby@coolpage.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 928243A696D for <hybi@core3.amsl.com>; Sun, 22 Aug 2010 16:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.225
X-Spam-Level:
X-Spam-Status: No, score=-2.225 tagged_above=-999 required=5 tests=[AWL=0.374, BAYES_00=-2.599]
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 gw9olCXMoZwO for <hybi@core3.amsl.com>; Sun, 22 Aug 2010 16:52:56 -0700 (PDT)
Received: from www5.webmail.pair.com (www5.webmail.pair.com [66.39.3.83]) by core3.amsl.com (Postfix) with SMTP id 9E2C03A68EA for <hybi@ietf.org>; Sun, 22 Aug 2010 16:52:56 -0700 (PDT)
Received: (qmail 77053 invoked by uid 65534); 22 Aug 2010 23:53:29 -0000
Received: from 121.97.54.174 ([121.97.54.174]) (SquirrelMail authenticated user shelby@coolpage.com) by sm.webmail.pair.com with HTTP; Sun, 22 Aug 2010 19:53:29 -0400
Message-ID: <355ce61a22f2c506569145230eee7c8b.squirrel@sm.webmail.pair.com>
In-Reply-To: <AANLkTimWTRw6zSWDbDg4JH9UBv-2a=S5obX2+jbLpGDL@mail.gmail.com>
References: <AANLkTimKbmcpgx8k0uXUWvCO=8w9pPrtV=3y4qh6363k@mail.gmail.com> <b95f074b65875865802f532bb5668ff2.squirrel@sm.webmail.pair.com> <AANLkTi=AXLFPSASV2zkBiUU=1StO=YSrKq_9AZ2ZnVHy@mail.gmail.com> <8cd6ecfebb4a073ecf94c8e1aa56e642.squirrel@sm.webmail.pair.com> <77aecf89c6c8673f1b999f80fa04e005.squirrel@sm.webmail.pair.com> <AANLkTik9tpCQr9LjK0qdLuA1KfJv1MN9yK2UZ1ytxfCW@mail.gmail.com> <fb8bfae1b88ade55cad4234af724004b.squirrel@sm.webmail.pair.com> <AANLkTimAu5de0PnujHRwR0nnXFBpqdJoRWZ=UvGrLVJ7@mail.gmail.com> <65fc5176b7cc6c775ec167f4404b43ed.squirrel@sm.webmail.pair.com> <bf7fd641553e15431d35d7352d023df2.squirrel@sm.webmail.pair.com> <AANLkTin=urXr0eAg3mrXfnCm5jQDb6yLSpkF-QLNQYq+@mail.gmail.com> <ef16e51dbbd45c735d21ce310063cf36.squirrel@sm.webmail.pair.com> <AANLkTimP6KOU49B_dhZhibJJ0-Mf0KkETfLLvEBcf85N@mail.gmail.com> <ef6d11756d22e21402bc1af152916120.squirrel@sm.webmail.pair.com> <AANLkTimWTRw6zSWDbDg4JH9UBv-2a=S5obX2+jbLpGDL@mail.gmail.com>
Date: Sun, 22 Aug 2010 19:53:29 -0400
From: Shelby Moore <shelby@coolpage.com>
To: John Tamplin <jat@google.com>
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] frame length encoding
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: shelby@coolpage.com
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Aug 2010 23:52:57 -0000

> On Sun, Aug 22, 2010 at 6:58 PM, Shelby Moore <shelby@coolpage.com> wrote:
>
>> That forces the receiver to check for the larger size.  See my prior
>> post
>> on the multi-core issue, that it would be more efficient in that case if
>> the sender honored the maximum.
>>
>> Why can't the sender honor the agreed maximum size?
>>
>
> The receiver will still have to check, because the sender might be an
> attacker hoping to take advantage of a receiver that only checks the first
> 2
> bytes of the length while firewalls/etc would have filtered it had it been
> correct.  Getting different entities to make different decisions about
> some
> framing of data is a fundamental attack tactic.

Isn't that incorrect logic?

If the spec says that the maximum is the maximum, then firewall should
respect the spec.

Any sender can send any thing any time.  That is not relevant here.