Follow

has been moving more towards the deb.debian.org mirror which is provided by a single CDN company, . It works well, but also feeds an enormous amount of to a single company, and it can be used to track computers and maybe even people. And the privacy policy in effect is unclear. Fastly says the policy of the "subscriber" applies, but the privacy policy for deb.debian.org is not listed anywhere I could find. Anyone have any insight here?

@eighthave there is also cdn-aws.deb.debian.org/ which used by AWS.

I think the deb.debian.org pointed to both previously, but now its only using fastly now.

@miyuru Does the AWS mirror have a clearer privacy policy somewhere? That front page is just as minimal as the Fastly one

@eighthave I don’t even know *why* this happened, really. I cannot imagine the mirror scripts/lists take that much effort to maintain. We’ll keep on providing a mirror and keep on only using what little logs there are for looking at faults or unusual usage.

@interpipes @eighthave Well, maintaining a list of geographically diverse, "blessed" mirrors of consistent quality (that is, good enough to have ftp.*.debian.org point at them without having too many users complain) does take a lot of effort, that noone seems to really be interested in sustaining. The Debian System Administrators (the people who maintain the debian.org systems, and on whom the maintenance of the mirror list has fallen "by default") have decided to focus on maintaining the backends for a couple of CDNs for the user-facing services blessed by debian.org instead.

mirror-master.debian.org/statu gives an idea of the breadth of the issue (for instance, look at the random assortment of versions for the sync scripts). That set of monitoring scripts is what's used to generate the list of mirrors that's shipped with the debian-installer.

As for the deb.debian.org fastly config, it's all in git: salsa.debian.org/dsa-team/mirr

@olasd @interpipes I understand why DSA would make that choice, I'm not faulting them. My goal is to raise awareness of the advantages and disadvantages of each approach, and to increase user privacy. That requires transparency about what happens with the data and metadata, and commitments from any organizations running the mirrors.

@eighthave @neil As far as I know Fastly chooses not to store logs but instead allows customers to have them forwarded directly to their own storage endpoint

@andydavies @neil that would be nice, do you have any documentation on that?

@eighthave @neil This is the clearest statement I know on the subject of customer request logs docs.fastly.com/en/guides/data

I’ve also had discussions with Fastly where they’ve talked about how they don’t want to store customer request log data for privacy reasons

@andydavies @neil I'm looking for actual privacy policies since those would be legally binding and the company could be help liable for violations. I've seen a lot of language like that, it promises little, since it has broad, vague exceptions like "except where explicitly stated in the Documentation and related to the functional performance of the services". Like, if some gov asks nicely for data, would handing it over be considered "functional performance of the services"?

@andydavies @neil Hi @eighthave we have a lot more information about our trust/ privacy practices and our ethical standards on our website: fastly.com/solutions/customer-

and our privacy/ data processing policies are on our website too:
fastly.com/privacy/
fastly.com/data-processing

@haubles @andydavies @neil thanks, I've read through those already, and it is still difficult for me to say what data about deb.debian.org Fastly actually keeps and for how long. Here are the policies of some other Debian mirrors, which are much simpler but perhaps leave out a couple key details like what log format they use.

* ftp.lysator.liu.se/datahanteri
* plug-mirror.rcac.purdue.edu/in
* mirror.fcix.net/policy/
* mirror.ossplanet.net/

Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml