Re: Scope for self-destructing email?

Warren Kumari <warren@kumari.net> Thu, 17 August 2017 00:44 UTC

Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB3871323B8 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 17:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 AxYqzNqI-k8m for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 17:44:12 -0700 (PDT)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28CA1132386 for <ietf@ietf.org>; Wed, 16 Aug 2017 17:44:12 -0700 (PDT)
Received: by mail-wr0-x233.google.com with SMTP id z91so20430374wrc.4 for <ietf@ietf.org>; Wed, 16 Aug 2017 17:44:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=F6b1ncl0/sRbFlWxJy5+VJZr6KSc96GQbfw5eXfVJ5Y=; b=NLL5hZsk7Kdu7vTB1i5sZ355sZO8saz55J/J0ubg4/1lMLvlT74OHhsoaOIllVMCGe CaKSLmsfgDRvxla5ZXu8yoU0AxfCYVNcTE614daTPYa4uyGY4QJdxZmJNXjSAD14XP70 GZAOf6Y2PZEF0GUr12UkTvMrvLGSIBkC82Axd2hsX8t61DsqMPjVZ7n5FIPIIYT6KyQZ 3JSTkyLAfGzRHacAk0DX48qFo7rjcjMWO5LGN9RE56NbpSoX4rl/ZcjfdqSHaXSbQOOu 7fnn/hVnxQHcXgnkfnTSsj9+FD4LM1nnlXOpYzdmW60Jp5wiCPmsjFQN0aGwTSCYIfnF 6hgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=F6b1ncl0/sRbFlWxJy5+VJZr6KSc96GQbfw5eXfVJ5Y=; b=Zn4yWabdYjW8Qks9SdwT8qyrYXzrrnptbModHICNakoSHaiAF3TQKdgnc1Y8rglPG4 VMxJXNKGiyxdgbCzN9LmmBTbAGtFoPnpRI/3DoQt1Gux6aAWkVIq2yktY18BhRnx97SM V/Gk6av7EytLykOLSm5vs3+5Xcf1O2NiAwDVlP/gkb88WvLbZcv1j4UKyS9xcNV+izgy enU0TRbXFRc/E7WjH8Jfa1umgQ1Tc2/qYInhVk/fSM3cQ3wJx2ob1Aqca5XERvfcd7S1 jMN7vDuC3FEZpP51HVsZNKNgGodUZNrvPeiH7hEjXod/pxua5QsPvJPHPtd1rEfjly7o mEGg==
X-Gm-Message-State: AHYfb5h4f1HL2ro2P8U4q3vGCkWNFleLAsZr4UAveY46YwYuKei29t61 tBx4VyIUjJ8M1uK6cqvRFrCm5S0X/FYN
X-Received: by 10.223.184.50 with SMTP id h47mr2234080wrf.163.1502930650630; Wed, 16 Aug 2017 17:44:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.164.135 with HTTP; Wed, 16 Aug 2017 17:43:29 -0700 (PDT)
In-Reply-To: <20170816225637.4431.qmail@ary.lan>
References: <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> <20170816225637.4431.qmail@ary.lan>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 16 Aug 2017 20:43:29 -0400
Message-ID: <CAHw9_iJdp2OCM8Otmj+bqZLp6QMGep6K+0+TnudSsmUCEfW1_Q@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: John Levine <johnl@taugh.com>
Cc: IETF Discuss <ietf@ietf.org>, vaibhav singh <vaibhavsinghacads@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VMgGFPacJbIOwm6wBMyoij4FDDA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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, 17 Aug 2017 00:44:15 -0000

On Wed, Aug 16, 2017 at 6:56 PM, John Levine <johnl@taugh.com> wrote:
> In article <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> you write:
>>This seems to work for me. Any problems which could come up with having a
>>central authority for this feature?
>
> Many.  What if I tell the central authority that I implement
> self-destructive e-mail but I'm lying?  How could the central
> authority tell?  I'm pretty sure I can pass whatever audits they make
> since they have no way to tell what data I'm hiding in places they
> can't see.
>

I suspect that one of my previous responses here might have been both
too subtle, and also quite likely to have been ignored as spam.
All of these sorts of solutions will always be subject to the issue
that you don't control the recipient system -- there is noting (well,
very little) that stops the recipient from taking a screen capture of
the message as it is displayed, or even whipping out their smartphone
and taking a picture of the screen.
See: http://www.owl-stretching-time.com/because-you-dont-contol-the-recipient.png
There is nothing that the sender can include which will make a image
of the message go "Boom" later.


>>4.) A really boiled down version of ephemeral mails could just mark the
>>mail "outdated" if the information provided in the mail is not expected to
>>hold good after some time, instead of actually expunging the mail.
>
> As others have said, that feature has come and gone many times in the past.  In
> netnews, which is similar in some ways to mail, there's an Expires: header which
> works reasonably well, typically used to mark messages that stop being interesting
> after some point like weather forecasts or event reminders.  There's no guarantee
> that anyone will follow the advice, and you certainly can't use it to force stuff
> to disappear, but it's been occasionally useful.

Yup - I think that an advisory note (Expire:) saying "This mail might
not be relevant anymore (it was an invitation to a party last week)"
has some (limited) value, but a: relying on something like this to
actually expunge information is unworkable and b: rude. I might want
to search my mail to see what the weather forecast said last Thursday,
or search event reminders to know where I was last Tuesday. Once
you've sent me the mail, it's mine!

W

>
> R's,
> John
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf