IETF Logo Mail Archive

Re: On email and web security

Doug Barton <dougb@dougbarton.us> Thu, 14 January 2016 04:26 UTC

Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7D41A8A64 for <ietf@ietfa.amsl.com>; Wed, 13 Jan 2016 20:26:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level:
X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 XkA-PnGkjZtp for <ietf@ietfa.amsl.com>; Wed, 13 Jan 2016 20:26:55 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18B421A8A62 for <ietf@ietf.org>; Wed, 13 Jan 2016 20:26:55 -0800 (PST)
Received: from [IPv6:2001:4830:1a00:8056:256e:3c74:d125:8cc1] (unknown [IPv6:2001:4830:1a00:8056:256e:3c74:d125:8cc1]) by dougbarton.us (Postfix) with ESMTPSA id 87D6A39D07 for <ietf@ietf.org>; Thu, 14 Jan 2016 04:26:52 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dkim; t=1452745614; bh=jNmy1pyUXt+ZH1/Y1tGTuZ36jBa8tLyihWFRbOdgmPY=; h=Subject:To:References:From:Date:In-Reply-To; b=Y6CnZTt+rzOzboUbzL5ae+gpDDGUFdHbwheMdWnG0Dc30wZvXeLQVb4bb71+IvAY8 12VhnNDccx0FRmuq2IK2Y7fF9kh0zjlSYIKYIw8dQVDFWH1hhPY8ZX68q7lXflDFdQ tuM7WvFm0pPST4QPi7dRoOD48MYenJ9YYGNbElBw=
Subject: Re: On email and web security
To: ietf@ietf.org
References: <20160114024314.66977.qmail@ary.lan>
From: Doug Barton <dougb@dougbarton.us>
Openpgp: id=E3520E149D053533C33A67DB5CC686F11A1ABC84
Message-ID: <56972387.608@dougbarton.us>
Date: Wed, 13 Jan 2016 20:26:47 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <20160114024314.66977.qmail@ary.lan>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0LxgVPTqeZfIx7pNIwoEPfi2I-E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2016 04:26:56 -0000

On 01/13/2016 06:43 PM, John Levine wrote:
>> Well the question I responded to was wondering if there was a way to
>> have the list software re-encrypt to the members without being able to
>> decrypt the message first. If I understand correctly, you're saying that
>> S/MIME can't do that either?
>
> Not unless there is something hidden inside all of the X.509 glop that
> I'm unaware of.  Message bodies are encrypted with a session key
> which is in turn encrypted with the public keys of the message
> recipients.  Nothing magic there.

Right-O, thanks for clarifying. :)

v2.23.0 | Report a Bug | By Email