Skip to content

Issues: w3cping/tracking-issues

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
29 Open 11 Closed
29 Open 11 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

status list index is a persistent cross-origin identifier close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#450 opened Mar 7, 2024 by w3cbot
mitigations for risk of unique status lists close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#449 opened Mar 7, 2024 by w3cbot
caching status lists as a mitigation for identifying when the holder visited a verifier close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#448 opened Mar 7, 2024 by w3cbot
anonymizing proxy rather than CDN as a privacy mitigation close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#447 opened Mar 7, 2024 by w3cbot
information revealed by status updates close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#446 opened Mar 7, 2024 by w3cbot
when revocation status is and isn't appropriate to present close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#445 opened Mar 7, 2024 by w3cbot
comparison with alternative revocation mechanisms close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#444 opened Mar 7, 2024 by w3cbot
status list index randomization requirement close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#443 opened Mar 7, 2024 by w3cbot
describe dummy or decoy entries as a privacy mitigation close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-bitstring-status-list missing link wg:vc https://www.w3.org/groups/wg/vc
#442 opened Mar 7, 2024 by w3cbot
Clarify how holders can detect or prevent privacy problems. pending Issue created by the tracker tool and may need to be refined s:vc-di-bbs missing link tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#439 opened Feb 2, 2024 by w3cbot
Security and Privacy Self Review pending Issue created by the tracker tool and may need to be refined s:vc-di-bbs missing link tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#434 opened Dec 16, 2023 by w3cbot
Security and Privacy Self-Review Questionnaire close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-jose-cose missing link tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#421 opened Sep 15, 2023 by w3cbot
Encourage the use of OHTTP close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-data-model https://w3c.github.io/vc-data-model/ tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#418 opened Sep 5, 2023 by w3cbot
Point Privacy and Security Considerations section back to Data Integrity close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-di-eddsa https://w3c.github.io/vc-di-eddsa/ tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#415 opened Aug 27, 2023 by w3cbot
Highlight security/privacy trade-offs between RDF-CANON and JCS close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-di-eddsa https://w3c.github.io/vc-di-eddsa/ tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#414 opened Aug 27, 2023 by w3cbot
Add reference back to VC Data Model Security and Privacy Considerations sections close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-data-integrity https://w3c.github.io/vc-data-integrity/ tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#413 opened Aug 19, 2023 by w3cbot
Add Privacy Consideration for previous signers in proof chains close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-data-integrity https://w3c.github.io/vc-data-integrity/ tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#412 opened Aug 19, 2023 by w3cbot
Add normative guidance that @context files SHOULD be cached close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-data-integrity https://w3c.github.io/vc-data-integrity/ tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#411 opened Aug 19, 2023 by w3cbot
Point Privacy and Security Considerations section back to Data Integrity close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-di-ecdsa https://w3c.github.io/vc-di-ecdsa/ wg:vc https://www.w3.org/groups/wg/vc
#410 opened Aug 19, 2023 by w3cbot
Highlight security/privacy trade-offs between RDF-CANON and JCS close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-data-integrity https://w3c.github.io/vc-data-integrity/ wg:vc https://www.w3.org/groups/wg/vc
#409 opened Aug 19, 2023 by w3cbot
Add guidance on inclusion of unique tracking identifiers close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-json-schema https://w3c.github.io/vc-json-schema/ wg:vc https://www.w3.org/groups/wg/vc
#408 opened Aug 18, 2023 by w3cbot
Add guidance for wallets when using JsonSchemaCredential and selected disclosure close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-json-schema https://w3c.github.io/vc-json-schema/ wg:vc https://www.w3.org/groups/wg/vc
#407 opened Aug 18, 2023 by w3cbot
Encourage usage of OHTTP during schema resolution close? The related issue was closed by the Working Group needs-resolution PING expects this item to be resolved to their satisfaction. pending Issue created by the tracker tool and may need to be refined s:vc-json-schema https://w3c.github.io/vc-json-schema/ wg:vc https://www.w3.org/groups/wg/vc
#406 opened Aug 18, 2023 by w3cbot
Address Metadata-Driven Correlation close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-data-model https://w3c.github.io/vc-data-model/ tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#404 opened Aug 17, 2023 by w3cbot
Mitigating Location Correlation via Common Issuers close? The related issue was closed by the Working Group pending Issue created by the tracker tool and may need to be refined s:vc-data-model https://w3c.github.io/vc-data-model/ tracker PING is following a discussion, but doesn't require resolution. wg:vc https://www.w3.org/groups/wg/vc
#402 opened Aug 17, 2023 by w3cbot
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.