1994-02-15 - Detweiler abuse again

Header Data

From: hughes@ah.com (Eric Hughes)
To: cypherpunks@toad.com
Message Hash: 722da6dcb63292aae36a0f43aa69f1e4df4e110bfbcbed0fc1b8afb5819cd8e5
Message ID: <9402151753.AA22610@ah.com>
Reply To: <199402151730.JAA06052@jobe.shell.portal.com>
UTC Datetime: 1994-02-15 18:01:41 UTC
Raw Date: Tue, 15 Feb 94 10:01:41 PST

Raw message

From: hughes@ah.com (Eric Hughes)
Date: Tue, 15 Feb 94 10:01:41 PST
To: cypherpunks@toad.com
Subject: Detweiler abuse again
In-Reply-To: <199402151730.JAA06052@jobe.shell.portal.com>
Message-ID: <9402151753.AA22610@ah.com>
MIME-Version: 1.0
Content-Type: text/plain


>I'm not sure Eric's idea about connecting via sockets would eliminate all
>possibilities of logging.  

I did not mean to imply this.  Using daemons would get rid of the
_default_ loging that occurs on systems.  Changing logging from
opt-out to opt-in would make a large practical difference right now.

>It seems that with telnet, at least, the systems
>that you connect to are able to find your host name.  Still, host names
>would be more private than full addresses.

This was exactly my point in a previous article.  An email address
identifies both a machine and a user, where an IP connection (e.g.
telnet) only reveals the machine.  Now if the sysadmin of the
originating machine logs and shares information with the destination
machine, the user can be identified.  But again, this is an opt-in
monitoring system.

Eric





Thread