-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
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
ProTip!
Exclude everything labeled
bug
with -label:bug.