IETF Logo Mail Archive

Re: On email and web security

Doug Barton <dougb@dougbarton.us> Thu, 14 January 2016 00:34 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 C9B2B1AD066 for <ietf@ietfa.amsl.com>; Wed, 13 Jan 2016 16:34:51 -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 M5eyH2I3sb2y for <ietf@ietfa.amsl.com>; Wed, 13 Jan 2016 16:34:50 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) (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 2B9BA1A87CD for <ietf@ietf.org>; Wed, 13 Jan 2016 16:34:50 -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 8800C39D07 for <ietf@ietf.org>; Thu, 14 Jan 2016 00:34:48 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dkim; t=1452731689; bh=bCj7x0KxLa926qM024BtxMWMyCrpyhicEEN2yWtLzWc=; h=Subject:To:References:From:Date:In-Reply-To; b=VL/n29csY6earenRNbBX56l3oVg9LhdN1KM/83rTLu7CUXZD1kZJh9a/4CyLsLrkS i/5ITO9k/vdUUOApBrTOBaNQSJ5BHyh4ytpuEZK+63aq7vWl9CEn7ZFfgeKmQytcPj WyVaLAgseo24JmLMXCpb0BXjj2p2gfzlEiVIfmnM=
Subject: Re: On email and web security
To: ietf@ietf.org
References: <20160113233002.66489.qmail@ary.lan>
From: Doug Barton <dougb@dougbarton.us>
Openpgp: id=E3520E149D053533C33A67DB5CC686F11A1ABC84
X-Enigmail-Draft-Status: N1110
Message-ID: <5696ED21.6000805@dougbarton.us>
Date: Wed, 13 Jan 2016 16:34:41 -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: <20160113233002.66489.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/eV9ipIIxYffNY0ZSH0LORQKphcU>
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 00:34:51 -0000

On 01/13/2016 03:30 PM, John Levine wrote:
>> I don't see any way that this could work using PGP, but I confess I
>> don't know enough about S/MIME to know if it could be done using it or not.
>
> The one list manager that I know of that actually does S/MIME, Sympa,
> sends a separate copy of the message to each recipient encrypted to
> his key.

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?

Doug

v2.27.8 | Report a Bug | By Email | System Status