From owner-freebsd-chat Thu Feb 13 5:14:17 2003 Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 456CC37B401 for ; Thu, 13 Feb 2003 05:14:16 -0800 (PST) Received: from pollux.asml.nl (ns.asml.nl [195.109.200.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EF6443F75 for ; Thu, 13 Feb 2003 05:14:13 -0800 (PST) (envelope-from brad.knowles@skynet.be) Received: from nlvdhv01.asml.nl (nlvdhv01 [195.109.200.68]) by pollux.asml.nl (8.8.8+Sun/8.8.8) with SMTP id OAA28478; Thu, 13 Feb 2003 14:14:06 +0100 (MET) Received: from unknown(146.106.1.223) by nlvdhv01.asml.nl via csmap id 11534; Thu, 13 Feb 2003 14:12:54 +0100 (CET) Received: from titan.asml.nl (titan [146.106.1.9]) by creon.asml.nl (8.11.6+Sun/8.11.6) with ESMTP id h1DDE6c14666; Thu, 13 Feb 2003 14:14:06 +0100 (MET) Received: from [10.0.1.2] (frobozz.asml.nl [146.106.12.76]) by titan.asml.nl (8.9.3+Sun/8.9.3) with ESMTP id OAA16012; Thu, 13 Feb 2003 14:14:06 +0100 (MET) Mime-Version: 1.0 X-Sender: bs663385@pop.skynet.be Message-Id: In-Reply-To: <3E4B12F5.2608BBB@mindspring.com> References: <20030211032932.GA1253@papagena.rockefeller.edu> <3E498175.295FC389@mindspring.com> <3E49C434.D8D497EE@mindspring.com> <3E4A83BC.8A15E7C3@mindspring.com> <3E4B12F5.2608BBB@mindspring.com> Date: Thu, 13 Feb 2003 14:00:08 +0100 To: Terry Lambert From: Brad Knowles Subject: Re: Email push and pull (was Re: matthew dillon) Cc: Brad Knowles , Rahul Siddharthan , freebsd-chat@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 7:37 PM -0800 2003/02/12, Terry Lambert wrote: >> This problem is already solved -- check out Perdition. > > The problem is *not* solved by Perdition. Perdition does not even > *begin* to solve the problem. Okay, what parts of the problem doesn't Perdition solve? >> You can do this today. Send an e-mail and tell people to go read >> a specific USENET news message. Doesn't work too well. > > Doesn't address any privacy issues. Even encrypted, your data is > out there for anyone to perform traffic analysis upon. I don't see how you can do a flood-fill mechanism without having the message accessible to anyone who'd want to read it. Of course, it should be public-key encrypted, so that the only traffic analysis that could be performed was the path that it took over the flood-fill servers, which could be obscured. -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message