From owner-freebsd-chat  Wed Oct  8 16:08:09 1997
Return-Path: <owner-freebsd-chat>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA21220
          for chat-outgoing; Wed, 8 Oct 1997 16:08:09 -0700 (PDT)
          (envelope-from owner-freebsd-chat)
Received: from shasta.wstein.com (joes@shasta.wstein.com [207.173.11.132])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA21215
          for <chat@FreeBSD.ORG>; Wed, 8 Oct 1997 16:08:04 -0700 (PDT)
          (envelope-from joes@shasta.wstein.com)
Received: (from joes@localhost)
	by shasta.wstein.com (8.8.7/8.8.7) id QAA05319;
	Wed, 8 Oct 1997 16:06:20 -0700 (PDT)
From: Joseph Stein <joes@seaport.net>
Message-Id: <199710082306.QAA05319@shasta.wstein.com>
Subject: Re: group assignments from make world.
In-Reply-To: <199710080605.PAA01099@word.smith.net.au> from Mike Smith at "Oct 8, 97 03:35:41 pm"
To: mike@smith.net.au (Mike Smith)
Date: Wed, 8 Oct 1997 16:06:20 -0700 (PDT)
Cc: chat@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31H (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-chat@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Encrypt the CVSup output based on a key posted weekly to the relevant 
> lists.  Change the key frequently.

Which would work dually:  it would (not necessarily) force those users
that wanted the key to use the website's search function to find it.

Perhaps a header line should be embedded that says 'do not archive this
in the search engine.'

Other than that, I'm all for it.

(How about just adding the cryptography to CVSup and you can't connect to
the server without the appropriate password...)

joe