Re: [apps-discuss] update to rfc5965

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 08 July 2013 05:08 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9D5321F9DD6 for <apps-discuss@ietfa.amsl.com>; Sun, 7 Jul 2013 22:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RQ4uEG10vS4I for <apps-discuss@ietfa.amsl.com>; Sun, 7 Jul 2013 22:08:12 -0700 (PDT)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1324521F9DC0 for <apps-discuss@ietf.org>; Sun, 7 Jul 2013 22:08:11 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id q56so3301752wes.17 for <apps-discuss@ietf.org>; Sun, 07 Jul 2013 22:08:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=E7V/C1xAufTt4Fd8pWQZ79alZWltVL7hlTe7gg5mdO8=; b=fJmRprPEWII+ZEVKjPvb8l5J0iQF1CIhPqCYaaDmPTgZZh1nwMnLvEalPsYLhb5RoQ LrYPfjlKF/DAa8RoAaTx5s4gSlOGATLW5d/hK5OEzX8JN+25C3XVbFDgBHOPTwEN/cfE 4uxw8jV/aybE1pS5CkQYnACdhzQ5OdzRe4RJyCJhpGeGUZ6WH3geuLsZLbKCRF38WQ0B QRsao9DJn0HE8nRkl1F9Fb3xwdpinVElVzBKhTeFxYAQe/fWIOTwhkD5ieHg5JSTowMN rVgfKFkUZSOB4OI8wyvFFdGlhGmIC/0UQGQ/xqly38NxwL+ZcpADM4JIjZqAJ7wHSEP1 ZM3w==
MIME-Version: 1.0
X-Received: by 10.180.187.209 with SMTP id fu17mr10560781wic.52.1373260091051; Sun, 07 Jul 2013 22:08:11 -0700 (PDT)
Received: by 10.180.90.16 with HTTP; Sun, 7 Jul 2013 22:08:10 -0700 (PDT)
In-Reply-To: <wW50zji0Cjq-qcVamEGefKY_jWvMFlBM9Ib9atm-pRAw1ZqYU@smtp.gmail.com>
References: <769743608.173673.1373148450418.JavaMail.zimbra@peachymango.org> <47488958.173803.1373149894362.JavaMail.zimbra@peachymango.org> <CAL0qLwZaPrXhnCXcMPzE6gcif6akV2iKibvXPrqHREE0hXPFrg@mail.gmail.com> <wW50zji0Cjq-qcVamEGefKY_jWvMFlBM9Ib9atm-pRAw1ZqYU@smtp.gmail.com>
Date: Sun, 07 Jul 2013 22:08:10 -0700
Message-ID: <CAL0qLwaE_+d7mHNe91xiX5GAYV-Q7w=wDVtC3cW6xzrubCn1AA@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary="001a11c269ace956a904e0f907e4"
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] update to rfc5965
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2013 05:08:12 -0000

On Sun, Jul 7, 2013 at 8:31 AM, Dave Cridland <dave@cridland.net> wrote:

> I would worry that the same problem Franck's trying to workaround here
> would resurface. That is, scanners would read "inside" the ZIP. Of course,
> maybe they would anyway with a specific media type and a known password.
>
>  I don't think that a fixed password in this instance is wrong, given the
> purpose of the encryption is not actually to encrypt, per-se.
>
>  I have to wonder if there's an alternative, like a media type that is
> itself defined as base64 encoded, but I note Franck's statement that a ZIP
> with a known password is the deployed workaround; standardizing this
> running code seems like the simplest option.
>
>
I'm just thinking that if the common practice shifts to using a different
password, now we need a new RFC that updates the other one.  That doesn't
seem to me to be scalable.

Maybe what we need is a media type whose definition spells out the fact
that the encoding is meant to obscure the content from everything except
analysis software.

-MSK