From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3c40499ff07580eac92ecdf0d66c173d@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pathetic
From: Geoff Collyer <geoff@collyer.net>
In-Reply-To: <1375223f3c7bef6420b98302686aca19@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Fri, 27 Feb 2004 15:36:41 -0800
Topicbox-Message-UUID: 014f915c-eacd-11e9-9e20-41e7f4b1d025

I'd be happy to accept public keys for authentication, but don't yet
have good ideas for how to get people to generate key pairs nor how to
distribute their public keys.  PGP hasn't taken over the world (though
it might do a little better if Apple were to integrate it with their
mail client seamlessly).

I'm willing to trust the remote IP address of a TCP connection as
identification.  The tuple of (remote IP address, claimed From:
address, recipient) should be enough to decide if I want a message,
especially if software doesn't have to decide accept-or-reject while
the sender is connected but has the third option of saying `hold it
until the recipient decides (or 10 days have elapsed)'.  For example,
I know that mail from 9fans-admin@cse.psu.edu *or* to
geoff.9fans@collyer.net should come from 130.203.4.6
(mail.cse.psu.edu) only.