Re: [Asrg] CRI Header

waltdnes@waltdnes.org Sat, 14 June 2003 03:54 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04739 for <asrg-archive@odin.ietf.org>; Fri, 13 Jun 2003 23:54:04 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5E3rZc18244 for asrg-archive@odin.ietf.org; Fri, 13 Jun 2003 23:53:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5E3rUm18237 for <asrg-web-archive@optimus.ietf.org>; Fri, 13 Jun 2003 23:53:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04700; Fri, 13 Jun 2003 23:53:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19R24T-0003sC-00; Fri, 13 Jun 2003 23:51:17 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19R24T-0003s8-00; Fri, 13 Jun 2003 23:51:17 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DLx1a25163; Fri, 13 Jun 2003 17:59:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DLwSm25134 for <asrg@optimus.ietf.org>; Fri, 13 Jun 2003 17:58:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24565 for <asrg@ietf.org>; Fri, 13 Jun 2003 17:58:24 -0400 (EDT)
From: waltdnes@waltdnes.org
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QwWu-0001cb-00 for asrg@ietf.org; Fri, 13 Jun 2003 17:56:16 -0400
Received: from dci.doncaster.on.ca ([66.11.168.194] helo=smtp.istop.com) by ietf-mx with esmtp (Exim 4.12) id 19QwWu-0001cY-00 for asrg@ietf.org; Fri, 13 Jun 2003 17:56:16 -0400
Received: from waltdnes.org (ip2-165.tor.istop.com [66.11.165.2]) by smtp.istop.com (Postfix) with SMTP id A671F36B9A for <asrg@ietf.org>; Fri, 13 Jun 2003 17:58:24 -0400 (EDT)
Received: by waltdnes.org (sSMTP sendmail emulation); Fri, 13 Jun 2003 17:58:42 -0400
To: ASRG list <asrg@ietf.org>
Subject: Re: [Asrg] CRI Header
Message-ID: <20030613215842.GA5964@m433>
References: <MBEKIIAKLDHKMLNFJODBOEBEFIAA.eric@purespeed.com> <01C32D56.08AC8FF0.eric@infobro.com> <MBEKIIAKLDHKMLNFJODBOEBEFIAA.eric@purespeed.com> <5.2.0.9.2.20030612142712.00b53008@std5.imagineis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5.2.0.9.2.20030612142712.00b53008@std5.imagineis.com>
User-Agent: Mutt/1.4.1i
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Fri, 13 Jun 2003 17:58:42 -0400

On Thu, Jun 12, 2003 at 02:32:47PM -0400, Yakov Shafranovich wrote
> At 10:50 PM 6/10/2003 -0400, waltdnes@waltdnes.org wrote:

> >  2) Yes, I realize that the ISP's MTA will have to keep state
> >information regarding the luser's preferences.  However, it comes down
> >to either a) ISP's server doing it (maybe luser enters pre-emptive
> >             whitelist/blocklist via web interface), or
> >          b) luser administering it on his own MUA (Aunt Ethel or your
> >             parents, yeah sure)
> 
> Privacy issues are a big concern here. Keep in mind that in the
> USA, this information can be subpoened by many parties ranging from
> the RIAA seeking copyright pirates to the FBI via the FBIS. Some
> approaches here such as using checksums, one way functions,
> cryptography, etc. are needed.

  Given those powers, I'd subpeona the ISP's logs instead, or at least a
subset generated by grepping for the suspect's email address as the
destination.  Spam Rule #3, or some corollary thereof, applies to
"military intelligence".  They're stupid and incompetent, and think that
the bad guys are too.  Assuming that...
  a) I was a bad guy, and
  b) I'd do something as silly as sending instructions via email
  I could...
  - subscribe to this list
  - whitelist envelope-sender "asrg-admin@ietf.org"
  - tell my co-conspirator to forge "asrg-admin@ietf.org" as the
    envelope-sender when emailing me

  My whitelist would look very innocent, and "military intelligence"
would still have to take a good look at the ISP's logs to figure our
what was going on.  Even simpler, we'd set up as spammers, and *NOT* use
tight whitelists.  Specially coded porno spams that open a dozen browser
windows would also open one which had a porno gif with steganographic
embedded encoding of instructions.

-- 
Walter Dnes <waltdnes@waltdnes.org>
Email users are divided into two classes;
1) Those who have effective spam-blocking
2) Those who wish they did
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg