IETF Logo Mail Archive

Re: [hybi] Upgrade Mechanism and HasMat (was Re: Extensibility mechanisms?)

John Tamplin <jat@google.com> Thu, 22 July 2010 21:50 UTC

Return-Path: <jat@google.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 C05753A67FB for <hybi@core3.amsl.com>; Thu, 22 Jul 2010 14:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level:
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 OAIz7nDU1Ts1 for <hybi@core3.amsl.com>; Thu, 22 Jul 2010 14:50:55 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 6D1613A6891 for <hybi@ietf.org>; Thu, 22 Jul 2010 14:50:55 -0700 (PDT)
Received: from wpaz37.hot.corp.google.com (wpaz37.hot.corp.google.com [172.24.198.101]) by smtp-out.google.com with ESMTP id o6MLpChF014741 for <hybi@ietf.org>; Thu, 22 Jul 2010 14:51:12 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1279835472; bh=H1AyNurKBEtTtZOkN5pIVAgxhww=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=pAWJ0i6jYY2Lr1RW4AjKMSJULmq/SOF+MY3lANcNWa1bm8XVrk3sbN1ZRMXwHAwgI w5WSHqrk2iyoHjeIr6u9Q==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=erCQYwR+6RwmU9yLxH/hFRc2IG6nY0WAN67NodiXJTs6EtRM9JRQiz/fawio9IR14 FGRjX/bAeHWGEFda7/Gyg==
Received: from gwj16 (gwj16.prod.google.com [10.200.10.16]) by wpaz37.hot.corp.google.com with ESMTP id o6MLpBjk024469 for <hybi@ietf.org>; Thu, 22 Jul 2010 14:51:11 -0700
Received: by gwj16 with SMTP id 16so415276gwj.28 for <hybi@ietf.org>; Thu, 22 Jul 2010 14:51:11 -0700 (PDT)
Received: by 10.151.133.2 with SMTP id k2mr4656169ybn.142.1279835471213; Thu, 22 Jul 2010 14:51:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.60.3 with HTTP; Thu, 22 Jul 2010 14:50:51 -0700 (PDT)
In-Reply-To: <168631FD-48D0-42C6-9E72-AF2FB3F9243E@gbiv.com>
References: <Pine.LNX.4.64.1007212153110.7242@ps20323.dreamhostps.com> <AANLkTiku76oSucTNDFdwgsFBNFa_cCpC-YktTnMfX47-@mail.gmail.com> <4C479130.4020500@caucho.com> <AANLkTikLDjBP-Xs5t6TxmJuq4nG8jwThQ=n34B4cEmup@mail.gmail.com> <4C479CE4.6070805@caucho.com> <AANLkTims1er0Rbv0ysP4gRs1Kd0He8hapHeJ3nON=JQa@mail.gmail.com> <4C47C5B0.3030006@caucho.com> <AANLkTi=ND-FOH8OoD=TCbiyeSZ-h0LhxQBXN5w-2hfvj@mail.gmail.com> <20100722055452.GL7174@1wt.eu> <AANLkTik_rpxo=1OfzHkwpC5soQG_NxvGuZNXx7gdhVTh@mail.gmail.com> <20100722064945.GM7174@1wt.eu> <AANLkTim7AsQGSwLE51uktj=B1vB6roZChAtDoCrE6fFG@mail.gmail.com> <4C47FF71.3050000@ericsson.com> <18E0FF9C-6C51-4602-92E1-E44802D0D8B5@gbiv.com> <AANLkTi=9npOTe+pC0YufDQcmMfuts9o7OW3k2crvUUqX@mail.gmail.com> <168631FD-48D0-42C6-9E72-AF2FB3F9243E@gbiv.com>
From: John Tamplin <jat@google.com>
Date: Thu, 22 Jul 2010 17:50:51 -0400
Message-ID: <AANLkTik0JQJnPe2wWq4aLGE7DCGwXPdJ-OCouAVJ5eNz@mail.gmail.com>
To: "Roy T. Fielding" <fielding@gbiv.com>
Content-Type: multipart/alternative; boundary="0016e6498998a20a42048c00eaa4"
X-System-Of-Record: true
Cc: hybi@ietf.org
Subject: Re: [hybi] Upgrade Mechanism and HasMat (was Re: Extensibility mechanisms?)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Thu, 22 Jul 2010 21:50:56 -0000

On Thu, Jul 22, 2010 at 5:03 PM, Roy T. Fielding <fielding@gbiv.com> wrote:

> You can even avoid the issue entirely, using HTTP,
> by implementing transfer-encoding and sending all message bodies
> compressed.


Actually, it probably wouldn't be that hard to construct plain-text which
would produce a given attack text as a substring of the compressed output,
and it might even give an attacker away to produce binary framing that they
otherwise would be unable to.

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.23.0 | Report a Bug | By Email