Re: Encryption simplification

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Mon, 31 October 2016 18:15 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41D851299A7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 31 Oct 2016 11:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.398
X-Spam-Level:
X-Spam-Status: No, score=-8.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 fJnZQjBvSBoV for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 31 Oct 2016 11:15:38 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B67701299AA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 31 Oct 2016 11:15:38 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1c1H43-0006nN-BA for ietf-http-wg-dist@listhub.w3.org; Mon, 31 Oct 2016 18:12:07 +0000
Resent-Date: Mon, 31 Oct 2016 18:12:07 +0000
Resent-Message-Id: <E1c1H43-0006nN-BA@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <hurtta@siilo.fmi.fi>) id 1c1H40-0006k4-07 for ietf-http-wg@listhub.w3.org; Mon, 31 Oct 2016 18:12:04 +0000
Received: from smtpvgate.fmi.fi ([193.166.223.36]) by titan.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from <hurtta@siilo.fmi.fi>) id 1c1H3t-0005Et-Lz for ietf-http-wg@w3.org; Mon, 31 Oct 2016 18:11:58 +0000
Received: from basaari.fmi.fi (basaari.fmi.fi [193.166.211.14]) (envelope-from hurtta@siilo.fmi.fi) by smtpVgate.fmi.fi (8.13.8/8.13.8/smtpgate-20161014/smtpVgate) with ESMTP id u9VIBR8P013868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 31 Oct 2016 20:11:27 +0200
Received: from shell.siilo.fmi.fi by basaari.fmi.fi with ESMTP id u9VIBQDL002295 ; Mon, 31 Oct 2016 20:11:27 +0200
Received: from shell.siilo.fmi.fi ([127.0.0.1]) by shell.siilo.fmi.fi with ESMTP id u9VIBQO5023570 ; Mon, 31 Oct 2016 20:11:26 +0200
Received: by shell.siilo.fmi.fi id u9VIBQJ9023569; Mon, 31 Oct 2016 20:11:26 +0200
Message-Id: <201610311811.u9VIBQJ9023569@shell.siilo.fmi.fi>
In-Reply-To: <CAP8-FqnvPOSDqYRNKqXy8TOVA5fAR32ZemsYof2z8Z2hLkTkmQ@mail.gmail.com>
References: <922b5d40-3c8e-4642-17ec-0034ff841d9d@gmx.de> <20161030182604.36ED312C6B@welho-filter3.welho.com> <CABkgnnUJhvt3NzUOYQ7fq9Twc8K65BtXroQ_LUHbranuqRv0mw@mail.gmail.com> <CAP8-FqneP57fhwQD1eFAw4D=PAe9uhtsjJ_2AqFAkZFTJcBJBQ@mail.gmail.com> <201610311654.u9VGsBGE021539@shell.siilo.fmi.fi> <CAP8-FqnvPOSDqYRNKqXy8TOVA5fAR32ZemsYof2z8Z2hLkTkmQ@mail.gmail.com>
To: Costin Manolache <costin@gmail.com>
Date: Mon, 31 Oct 2016 20:11:26 +0200 (EET)
Sender: hurtta@siilo.fmi.fi
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, Martin Thomson <martin.thomson@gmail.com>, Julian Reschke <julian.reschke@gmx.de>, HTTP working group mailing list <ietf-http-wg@w3.org>
X-Mailer: ELM [version ME+ 2.5 PLalpha43]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
X-Filter: smtpVgate.fmi.fi: 3 received headers rewritten with id 20161031/15871/01
X-Filter: smtpVgate.fmi.fi: ID 15878/01, 1 parts scanned for known viruses
X-Filter: basaari.fmi.fi: ID 151511/01, 1 parts scanned for known viruses
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (smtpVgate.fmi.fi [193.166.223.36]); Mon, 31 Oct 2016 20:11:27 +0200 (EET)
Received-SPF: none client-ip=193.166.223.36; envelope-from=hurtta@siilo.fmi.fi; helo=smtpVgate.fmi.fi
X-W3C-Hub-Spam-Status: No, score=-6.4
X-W3C-Hub-Spam-Report: AWL=0.010, BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.505, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1c1H3t-0005Et-Lz 5f8ec715394e11653ea66c29ad5ca30f
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Encryption simplification
Archived-At: <http://www.w3.org/mid/201610311811.u9VIBQJ9023569@shell.siilo.fmi.fi>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32757
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Costin Manolache <costin@gmail.com>om>: (Mon Oct 31 19:50:18 2016)
> I'm not sure I understand - if symmetric keys are used:
> 1. They should not be sent along with the content
> 2. If they are for some reason, it doesn't make a difference if it's in
> header or body

It makes difference with Out-Of-Band

> > https://greenbytes.de/tech/webdav/draft-reschke-http-oob-encoding-08.html#rfc.section.3.5.3

gives:

-------------------------------------------------
HTTP/1.1 200 OK
Date: Thu, 14 May 2015 18:52:00 GMT
Content-Encoding: aesgcm, out-of-band
Content-Type: text/plain
Encryption: keyid="a1"; salt="vr0o6Uq3w_KDWeatc27mUg"
Crypto-Key: keyid="a1"; aesgcm="csPJEXBYA5U-Tal9EdJi-w"
Content-Length: 101
Vary: Accept-Encoding

{
  "sr": [
    { "r" :
      "http://example.net/bae27c36-fa6a-11e4-ae5d-00059a3c7a00"}
  ]
}
-------------------------------------------------

Note that actual body, which was encrypted, is on
http://example.net/bae27c36-fa6a-11e4-ae5d-00059a3c7a00

That is different server than from where these headers
(and out-of-band -pointer on body) was got.


Story is that combination

    Content-Encoding: aesgcm, out-of-band

First encrypt body: aesgcm
Then move body out from response: out-of-band


/ Kari Hurtta