Restrict access to geolocation data in mirrorlist pages?

[stormi]

Hi,

GeoLite2's EULA is... convoluted (https://www.maxmind.com/en/geolite2/eula). Among the restrictions I think I understand from my reading, we're not allowed to make the data available to other people. However, through the mirrorlist and fromip parameters one can use mirrorbits to harvest parts of the data.

Would it be possible to add options to restrict access to such data?

Ideas:

• require a secret parameter, admin-defined, when the fromip parameter is given to a mirrorlist page.
• OR allow to never display details about the IP address location (city) in the mirrorlist page - can be done by altering the template ourselves I suppose, but maybe that's worth an option.
• OR a combination of both: if fromip is set, still display the mirrorlist page, but hide location details unless a secret is given

[ott]

Good point. Option 1 seems preferable to me. I don't see a use case where the fromip parameter would be useful for a normal user. It is most likely used by developers and perhaps administrators for diagnosis of problems with the mirror selection algorithm.