1996-11-25 - Re: kickouts done the Cypherpunks way…

Header Data

From: Moroni <moroni@scranton.com>
To: “Igor Chudov @ home” <ichudov@algebra.com>
Message Hash: 0b13eac830bbe37e43a93b86ed996643307586a646c22a69cab0826dc2a10878
Message ID: <Pine.LNX.3.95.961125032550.9643A-100000@user1.scranton.com>
Reply To: <199611250134.TAA23699@manifold.algebra.com>
UTC Datetime: 1996-11-25 08:28:29 UTC
Raw Date: Mon, 25 Nov 1996 00:28:29 -0800 (PST)

Raw message

From: Moroni <moroni@scranton.com>
Date: Mon, 25 Nov 1996 00:28:29 -0800 (PST)
To: "Igor Chudov @ home" <ichudov@algebra.com>
Subject: Re: kickouts done the Cypherpunks way...
In-Reply-To: <199611250134.TAA23699@manifold.algebra.com>
Message-ID: <Pine.LNX.3.95.961125032550.9643A-100000@user1.scranton.com>
MIME-Version: 1.0
Content-Type: text/plain


    The problem is that a nobody wanting to join the mailing list to learn
the subject matter of the list probably will not know anyone to sponsor
him.The second problem is that some isps go down occasionally and the mail
bounces back to the list which results in a subscription stop. How than
would one know to whom to go and ask for a recommendation. These  are
certainly things to consider .



On Sun, 24 Nov 1996, Igor Chudov @ home wrote:

> Date: Sun, 24 Nov 1996 19:34:09 -0600 (CST)
> From: "Igor Chudov @ home" <ichudov@algebra.com>
> To: cypherpunks@toad.com
> Subject: kickouts done the Cypherpunks way...
> 
> Hi,
> 
> Suppose Mr. X, owner of foobarpunks mailing list, wants to kick out Mr. Y,
> for his obnoxious letters to the mailing list.
> 
> Mr. X, however, is concerned that Mr. Y would subscribe through some
> proxy address and would continue replying to messages to foobarpunks.
> 
> It is assumed that the only person out of the whole universe, Mr. Y, 
> cannot be trusted. The problem is that X does not know which of the 
> subscribers is Mr. Y.
> 
> The question is, is there a technical way to disable Mr. Y from
> reading the list, or detect which subscription address is a proxy for Y?
> 
> If we assume that, at the moment when Y was kicked out, he was not
> subscribed through any other addresses, the solution becomes simple:
> for any new subscription request we require a letter of recommendation 
> from some other subscriber. Since other subscribers are presumed to
> be trustworthy, their recommendations would be sufficient. It is 
> actually being done in some of the mailing lists.
> 
> The problem becomes more complex when Mr. Y is already presumed to have
> infiltrated the mailing list, possibly through several proxy addresses.
> 
> Is there any way to detect/find which if the subscriber is Y? One of
> the simple-minded solutions is to _mutate_ mailing list messages
> so that all readers get slightly different copies of mailing list messages
> for each recipient. (Such mutations may include common misspellings,
> inserting spaces, etc)
> 
> If the mailing list bot keeps track of what changes were made in 
> messages to which individual, and if we assume that Mr. Y has to quote 
> significant parts of messages he replies to, finally the variations
> in messages may be reconciled with variations in quoted parts.
> 
> Mr. Y is not stupid, and may go as far as comparing letters, received
> through different proxy addresses, in order to detect "variations"
> and avoid quoting them.
> 
> The question is, is there a strategy of making variations and detecting
> them in quotes to finally catch Mr. Y?
> 
> 	- Igor.
> 
















       xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
       x   No success can compensate for failure in the home.  x
       x                                                       x
       xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx






Thread