Date: Wed, 9 Aug 2006 05:41:55 -0500 From: "Nikolas Britton" <nikolas.britton@gmail.com> To: "Igor Robul" <igorr@speechpro.com> Cc: freebsd-questions@freebsd.org Subject: Re: BSDstats Project v2.0 ... Message-ID: <ef10de9a0608090341l696b6ea3s2187f4b0a9b5fa6e@mail.gmail.com> In-Reply-To: <20060809072313.GA19441@sysadm.stc> References: <20060807003815.C7522@ganymede.hub.org> <20060808102819.GB64879@augusta.de> <20060808153921.V7522@ganymede.hub.org> <44D8EC98.8020801@utdallas.edu> <20060808201359.S7522@ganymede.hub.org> <44D91F02.90107@mawer.org> <20060808212719.L7522@ganymede.hub.org> <20060809072313.GA19441@sysadm.stc>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/9/06, Igor Robul <igorr@speechpro.com> wrote: > On Tue, Aug 08, 2006 at 09:30:42PM -0300, Marc G. Fournier wrote: > > Could create problems long term .. one thing I will be using the > > IPs to do is: > > > > SELECT ip, count(1) FROM systems GROUP BY ip ORDER BY count DESC; > > > > to look for any 'abnormalities' like todays with Armenia ... > > > > hashing it would make stuff like that fairly difficult ... > You can make _two_ hashes and then concatenate to form unique key. > Then you still be able to see "a lot of single IPs". Personaly, I dont > care very much about IP/hostname disclosure :-) I still like my idea the best for unique keys. It's a better way to detect hosts behind NATs, here it is again, four versions to pick from: # ifconfig | sha256 cbcc2f55a340c248af7e8a10871150d827af11d7051bbc782eefa04b0603248b # ifconfig | sha1 b607b9d45e6ad40c02ab20800e0d70245ab6db68 # ifconfig | md5 22a2a3eca61166fb113f1a688b3dd842 # ifconfig | cksum 3977021799 540 The only down side is it still can be faked, just like everything else. -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef10de9a0608090341l696b6ea3s2187f4b0a9b5fa6e>