1994-12-12 - Re: Broadcasts - addressing

Header Data

From: Adam Shostack <adam@bwh.harvard.edu>
To: db@Tadpole.COM (Doug Barnes)
Message Hash: 4670f0451236922452d127573a0a99c80f109950e4a19ed0be0b8b07721215ea
Message ID: <199412122127.QAA21293@bwnmr5.bwh.harvard.edu>
Reply To: <9412122018.AA07956@tadpole.tadpole.com>
UTC Datetime: 1994-12-12 21:27:39 UTC
Raw Date: Mon, 12 Dec 94 13:27:39 PST

Raw message

From: Adam Shostack <adam@bwh.harvard.edu>
Date: Mon, 12 Dec 94 13:27:39 PST
To: db@Tadpole.COM (Doug Barnes)
Subject: Re: Broadcasts - addressing
In-Reply-To: <9412122018.AA07956@tadpole.tadpole.com>
Message-ID: <199412122127.QAA21293@bwnmr5.bwh.harvard.edu>
MIME-Version: 1.0
Content-Type: text/plain


| 
| I have been contemplating how to mark broadcast messages as being 
| 'for' someone. To foil traffic analysis, you don't want to include 
| their nym or key-id, for the sake of the your poor CPU, you want to 
| avoid the need to attempt decryption on everything that passes through. 

	Keys are cheap.  Everyone should have a bunch.  To foil
TA, hand out a key to each correspondant.  Give them id's like
'latex.limb.malaise <alt.anonymous.mesages>'


Adam

-- 
"It is seldom that liberty of any kind is lost all at once."
						       -Hume





Thread