IETF Logo Mail Archive

Re: [perpass] draft-josefsson-email-received-privacy

"John R Levine" <johnl@taugh.com> Mon, 26 October 2015 14:31 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ABEF1B43D8 for <perpass@ietfa.amsl.com>; Mon, 26 Oct 2015 07:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.137
X-Spam-Level:
X-Spam-Status: No, score=-1.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 ZCjbSeOcH40X for <perpass@ietfa.amsl.com>; Mon, 26 Oct 2015 07:31:34 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06C2A1B43D6 for <perpass@ietf.org>; Mon, 26 Oct 2015 07:31:33 -0700 (PDT)
Received: (qmail 26195 invoked from network); 26 Oct 2015 14:31:34 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=6652.562e3946.k1510; bh=c8lDOj2uX81DMgNagGGt+oAVDrf2uZi//PkWa2zpD98=; b=SyUOC280jbDLRfQea9dZ7EYOT3OlYxi3nEWPYYGpS88d8WcksNocIpMh1PPBiPKIBuojEPFMTekdj9PaC42pOj/k4p0XoNj1N5qUekS2AZYEgDS5V+XFZmzAfmbw6QHqAqjKbIKjtD+FGf58sJkQB8KZQ5TkP6omBaFNy+5fbsZj3YVk5lgNVtYL3SFAyobkCpXKnJSvuNJ4NjiLeiRMrAJBV1DYuGpbaP/feObXzRJv7MswMr3m5S9h3ScMlSHZ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=6652.562e3946.k1510; bh=c8lDOj2uX81DMgNagGGt+oAVDrf2uZi//PkWa2zpD98=; b=JeTQTW3Fg9at9M0eNaPkF1fZb9XtDnAOQjGp6a1O8DfskDRjNEFEdCAw9pjjagwWEOd/a/L3/6wqFWPSeSmQeYoerCmladfz2oVGxF/UL+lNHC60Ug3XHPdRb6dwboSCJ1MrMDqiMo51B6Wz7bkTS2J1rzbdZzPuswkm9iiW7Vt7o3mGk/PcRmHA4k/+xheIiC/WIgD7QaPmNUAfy45vTvZ/9kv2BMhxpLyj/RzbT4lRNEkfOJ+EhnJO+dC1JK5L
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 26 Oct 2015 14:31:34 -0000
Date: Mon, 26 Oct 2015 10:31:32 -0400
Message-ID: <alpine.OSX.2.11.1510261028510.23347@ary.lan>
From: John R Levine <johnl@taugh.com>
To: Simon Josefsson <simon@josefsson.org>
In-Reply-To: <87pp02rprp.fsf@latte.josefsson.org>
References: <871tcl3f03.fsf@latte.josefsson.org> <20151024224621.15562.qmail@ary.lan> <0c5701d10f8f$882e4a10$988ade30$@huitema.net> <87pp02rprp.fsf@latte.josefsson.org>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/8uFvmD-5o_rDgY4t8mqyUAyC6P8>
Cc: perpass@ietf.org
Subject: Re: [perpass] draft-josefsson-email-received-privacy
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2015 14:31:35 -0000

> I am concerned about taking on a too wide scope.  I think it may be
> possible to reach closure on improving the Received header wrt privacy.

Perhaps, although all of that stuff is also useful for identifying sources 
of malware, phishing, and other online evils.

Assuming you agree that having someone's bank account credentials stolen 
is a privacy problem, this is not a simple question, and any simple answer 
is wrong.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

v2.23.0 | Report a Bug | By Email