1993-10-20 - Re: [TECH] defeating traffic analysis

Header Data

From: henry strickland <strick@osc.versant.com>
To: cme@ellisun.sw.stratus.com (Carl Ellison)
Message Hash: ead87e8db4e3c2d10aba50c6bcdc80080a4e5ee1e18e78f1a08f91b62be507f9
Message ID: <9310201810.AA27001@osc.versant.com>
Reply To: <9310201404.AA26853@ellisun.sw.stratus.com>
UTC Datetime: 1993-10-20 18:17:45 UTC
Raw Date: Wed, 20 Oct 93 11:17:45 PDT

Raw message

From: henry strickland <strick@osc.versant.com>
Date: Wed, 20 Oct 93 11:17:45 PDT
To: cme@ellisun.sw.stratus.com (Carl Ellison)
Subject: Re: [TECH] defeating traffic analysis
In-Reply-To: <9310201404.AA26853@ellisun.sw.stratus.com>
Message-ID: <9310201810.AA27001@osc.versant.com>
MIME-Version: 1.0
Content-Type: text/plain


# From: cme@ellisun.sw.stratus.com (Carl Ellison)
# 
# So:  have everyone send and receive exactly the same size message to/from the
# same sites at the same time every day.

That seems so unfortunate that the "average utilizaton" and the
"peak throughput" [I use quotes because I may have the wrong 
technical buzzwords, but you know what I mean] have to be
one and the same.

I've been trying to think of ways around that.  Am I wasting my time?

I've thought of trying to find probabilistic ways of letting you
vary how much your read/write to the net each day, maintaining
some constant statisics (average amount you read/write, standard
deviation, ...), that allows you one day to read a lot more than
the average, when you need to, without giving away that it was
useful information instead of padding. 

But I'm afraid it still gives away partial bits of information --
it is still likely that the hungriest readers and the most verbose
writers match up.

This becomes more on my mind, as I work on DCNet protocols.

References?  Advice?                    strick






Thread