Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TAP 19: should discuss privacy #178

Open
jku opened this issue Sep 6, 2023 · 1 comment
Open

TAP 19: should discuss privacy #178

jku opened this issue Sep 6, 2023 · 1 comment

Comments

@jku
Copy link
Member

jku commented Sep 6, 2023

While I was readin up on passim (a mDNS based content addressable storage) I noticed that their main use case fwupd does not use passim for artifact downloads because of privacy reasons: They don't want the other download "source" (which is potentially untrusted) to know which firmware files get downloaded.

I think TAP 19 should discuss the privacy implications as well: I think they exist in some form for all content addressable storage where the participants are not completely trusted (in comparison to traditional TUF where the privacy leak happens only to the relatively more trusted TUF artifact repository).

@joshuagl
Copy link
Member

Here's a blog post introducing Passim.

cc @adityasaky as the submitter of TAP 19.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants