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

How to think about “Developer Identity Privacy” #529

Open
abandon1234567 opened this issue Jan 5, 2025 · 1 comment
Open

How to think about “Developer Identity Privacy” #529

abandon1234567 opened this issue Jan 5, 2025 · 1 comment

Comments

@abandon1234567
Copy link

In Speranza (https://dl.acm.org/doi/pdf/10.1145/3576915.3623200) it is argued that Sigstore has a developer identity privacy leakage problem and a privacy friendly solution is proposed, but it also inevitably compromises the transparency that Sigstore provides.

How does everyone feel about transparency and privacy, please?

My personal view is that if transparency is compromised, there could be more serious security consequences.

@bobcallaway
Copy link
Member

Within Sigstore, we see dramatically higher usage of workload identity VS personal identity (via email). We'd like to continue to make privacy-related improvements for the use cases that require personal identity, but strongly encourage to use workload identity where possible.

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