Re: [saag] Input for conflict review of draft-secure-cookie-session-protocol

Barry Leiba <barryleiba@computer.org> Thu, 18 October 2012 17:22 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6490721F876A for <saag@ietfa.amsl.com>; Thu, 18 Oct 2012 10:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.088
X-Spam-Level:
X-Spam-Status: No, score=-103.088 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQLjALjQxawh for <saag@ietfa.amsl.com>; Thu, 18 Oct 2012 10:22:39 -0700 (PDT)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id BC62F21F875C for <saag@ietf.org>; Thu, 18 Oct 2012 10:22:38 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id n5so10695001oag.31 for <saag@ietf.org>; Thu, 18 Oct 2012 10:22:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Wz6oN2d+MOrYt9NI95j434wvQYgXQvnjn3DQEvcP9PY=; b=vHDTQDJzP4uv8MSYRAA/NOfZnsmkEQHQsr6UbON8DO8a8NnoIu3JuniRTRkVlXyIa7 QecwEtLOFxa+oFoKIrG3VRYInPE424yftmzzosv9WhORiNGdsOGZCDJ5co1kbXFNtQFJ kcsvW5yHgLUIG/CtwXHpAPcTaXlM2hUGWwTa+0MtrzK5mA+7cNKMskuBAvWMwQDSBmtO bYAJzWd4buxxRsdfDrmWDQjZwEy4uktDVPxW6lpD73g/Tg+JuqeGLjWODyijFqbT9KyP 3yuxRn0EAP5AbLNSXGZ84dc7zx3UErUxPduu8K3fVNMEq5Y6M63ntdNNgaNr0VexwGoH kuow==
MIME-Version: 1.0
Received: by 10.182.145.9 with SMTP id sq9mr17991519obb.42.1350580958429; Thu, 18 Oct 2012 10:22:38 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.76.82.5 with HTTP; Thu, 18 Oct 2012 10:22:38 -0700 (PDT)
In-Reply-To: <20121018171129.GO9392@1wt.eu>
References: <CALaySJK5JBo1cbsqcX6hyk0gSkDciZkX3o=o+rg9rgNVqBeRhw@mail.gmail.com> <20121018064805.GI7517@1wt.eu> <CAC4RtVBfZujwVN9NG1YyiCAm0yrV3Ufu+_SXtTJL4ZHC42tN6Q@mail.gmail.com> <20121018171129.GO9392@1wt.eu>
Date: Thu, 18 Oct 2012 13:22:38 -0400
X-Google-Sender-Auth: mw-TNYX936nGMFffVBIebyjqxq4
Message-ID: <CALaySJ+MDaeYNtNdMX8Qzu55xb_PFm6sup200nRHU2EaioEMhw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Willy Tarreau <w@1wt.eu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: saag@ietf.org
Subject: Re: [saag] Input for conflict review of draft-secure-cookie-session-protocol
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 17:22:39 -0000

> Well, maybe it's a matter of point of view. Adam took great care to
> rework the cookie spec and achieve RFC6265 with a number of usage
> recommendations to use cookies in the safest way. Since this draft
> suggests a usage which seems totally insecure to me, I found it
> appropriate to raise it as conflicting with the intended use of
> cookies. Maybe I was wrong, and if so please accept my apologises.
> Then it's unclear to me what kind of conflict should be raised :-/

True, and it's sometimes unclear to us as well.  I'll see your :-/ and
raise you a :-(

What we're looking for is this sort of thing:
- Is this document in direct conflict with current work in a working
group?  Which one(s)?
- Should this be handled by an existing working group?  Which one?
- Should a new working group be chartered for this, rather than doing
it as an Independent Submission?
- Does it appear that the authors are trying to get around the system
by submitting this to the ISE?
- Is this spec proposing something sufficiently harmful that it needs
proper IETF review to fix it?

I suppose your comments could be arguing for that last one.

But look at the list in RFC 5742, Section 3, and comment here on which
of the five responses you think applies to this document.  And then
definitely give your other feedback on the document to the ISE and the
document authors.

Thanks, Willy.

Barry