News for hackers. Stuff that matters.
Re:Changes to accessing and using Geolite2 databases by tyingq on Monday December 30, 2019 @01:13PM (#21915404)
That's pretty interesting that an IP address is enough to trigger CCPA. I thought it had to specifically tie to identity versus something broader like zip codes and city names to be covered under CCPA.

I wonder if you would be okay geolocating just the first three octets.

Re:Changes to accessing and using Geolite2 databases by throwaway95914 on Monday December 30, 2019 @01:35PM (#21915567)
Any identifier that can be deemed to identify a person or household is covered. This means IP address, tokens, uuid's, etc.

* IANAL

Re:Changes to accessing and using Geolite2 databases by frenchyatwork on Monday December 30, 2019 @02:24PM (#21915932)
Are there no zip codes in rural areas that are specific to a household?
Re:Changes to accessing and using Geolite2 databases by rubyfan on Monday December 30, 2019 @03:07PM (#21916225)
Zip5 codes are allocated by geography and population. See very large rural tracts of land in AZ or NM that have a large zip5 code area. Zip-9 probably could be associated with one household. Zips are actually a pain in the ass for purposes other than mail delivery because they change from time to time, are not cleanly allocated to geography or logical features on a map. They can be discontinuous and overlapping. Many companies employee proprietary means of assigning geographic identifiers that are not dependent on zip, population size or anything other than geo.

https://en.m.wikipedia.org/wiki/ZIP_Code

Re:Changes to accessing and using Geolite2 databases by tzs on Tuesday December 31, 2019 @01:46AM (#21919408)
To get a rough idea of how often a ZIP-9 narrows things down to a single street address, I took a look at the sales tax rate and boundary files made available for states that are in the Streamlined Sales Tax Agreement [1].

12 of those states, Arkansas, Georgia, Iowa, Kansas, Nebraska, North Carolina, Ohio, Oklahoma, South Dakota, Tennessee, Vermont, and Washington, use address-based tax rates. (The other 12 either just have one rate for the whole state, or just go by ZIP).

For each ZIP-9 in the address files for the 12 address-based states, I found the lowest and the highest street number for that ZIP-9. I then counted how many of the ZIP-9s had the lowest street number the same as the highest street number.

There were a total of 9,311,327 distinct ZIP-9 values.

2,415,305 of them had a low to high range that only included one number.

That's about 26% of the ZIP-9's having a unique street number. Note that this does not necessarily mean a single household, because I'm not looking at the full address. Apartment buildings, for instance, will in many cases show up in that 26%.

[1] https://www.streamlinedsalestax.org/Shared-Pages/rate-and-bo...

Re:Changes to accessing and using Geolite2 databases by rubyfan on Thursday January 02, 2020 @11:11PM (#21943073)
Excellent analysis. That’s like 2% or less of households in the US? So even at the Zip9 level not ideal for identifying specific households but problematic if you’re one of those 2M Zip9s.
Re:Changes to accessing and using Geolite2 databases by jimktrains2 on Monday December 30, 2019 @07:02PM (#21917831)
So, if I were to make this request behind Carrier grade Nat no one from that provider can be tracked?

Conversely, if my DHCP lease renewal I can be tracked?

Re:Changes to accessing and using Geolite2 databases by justinclift on Tuesday December 31, 2019 @07:42AM (#21920629)
Fairly sure this will be abused in short order by (say) places looking to tie an IP address to an account name which MaxMind is now saying they'll have going forwards.

eg think BitTorrent litigation trolls