From: Don <don@wero.cs.byu.edu>
Date: Sun, 14 Jan 96 22:14:17 PST
To: cypherpunks@toad.com
Subject: Re: (none) [httpd finding your identity]
In-Reply-To: <30F8596B.5611@netscape.com>
Message-ID: <199601150454.VAA00449@wero.cs.byu.edu>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

> I've removed the code that uses the e-mail address as the
> FTP password for anonymous FTPs.

Does that mean that general-purpose ftp won't be accepted unless the
user gives up their email? Greaaaaaaat... Can't have it both ways, I
guess. What can be added as far as user control; inline vs non-inline,
for example.

The FTP explanation certainly explains why my personal system is able
to confuse the username part of it. And I know there's nothing anyone
can do about the reverse-ip, but what about http referral field? Will
there be a way to turn off (blank, actually) this field?

Jeff, your efforts are certainly appreciated - your ability to get these
things done is most valuable.


Regarding the anonymizer:
First, are there any working anonymizers yet?
Second, is there any ISP that would be willing to give a home to the
  anonymizer?

Don
- -- 
<don@cs.byu.edu>           fRee cRyPTo!   jOin the hUnt or BE tHe PrEY
PGP key - http://students.cs.byu.edu/~don   or PubKey servers (0x994b8f39)
  June 7&14, 1995: 1st amendment repealed.  Junk mail to root@127.0.0.1
* This user insured by the Smith, Wesson, & Zimmermann insurance company *

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQB1AwUBMPneFsLa+QKZS485AQFq6gMAqAfHurwzZe9KTvmfWsg40iGubTHjlB2m
okvm6aHMjfOGRdHcSwD3sfSuuZ2suWS875qFDV06ITgbrWXJK3sb7lO9WPnU+0Of
8NFmEDZQNbQ8cqcio/NiT6PURp3NBc1+
=xQVe
-----END PGP SIGNATURE-----