[472] in athena10
Re: counterlog design discussion
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Wed Aug 27 14:53:02 2008
Date: Wed, 27 Aug 2008 14:52:18 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: ghudson@mit.edu
cc: athena10@mit.edu
In-Reply-To: <200808271637.m7RGbfZK017153@outgoing.mit.edu>
Message-ID: <alpine.DEB.1.10.0808271444210.1616@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Wed, 27 Aug 2008, ghudson@MIT.EDU wrote:
> a machine identifier which survives reinstalls and IP address changes.
How is this generated? What is considered as a reinstall and what is
considered a distinct machine? What happens with live CDs?
> I don't think there's a privacy issue since machines are already
> phoning home for package updates.
Tracking machines with a unique identifier that's different information
from what we already have (IP address, MAC address mapping via dhreg,
webserver logs) is an additional privacy issue, although perhaps not much.
> * Use nc to transmit a network syslog packet to wslogger. I
> don't know how hard this is since I'm not sure what network
> protocol syslog uses. It might be harder to implement (1a)
> this way since SIPB doesn't run a logging server.
syslog is a very simple UDP protocol. Try `echo '<3>test' | nc -q0 -u
localhost syslog`.
SIPB has syn, an underused server that's supposed to become a
general-purpose logging and monitoring server. We can configure it to
syslog into AFS easily.
--
Geoffrey Thomas
geofft@mit.edu
