issues
search
w3cping
/
tracking-issues
Repo to track PING initiated issues on other standards documents.
https://w3c.github.io/horizontal-issue-tracker/?repo=w3cping/tracking-issues
12
stars
2
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add Privacy Consideration for previous signers in proof chains
#412
w3cbot
opened
10 months ago
0
Add normative guidance that @context files SHOULD be cached
#411
w3cbot
opened
10 months ago
0
Point Privacy and Security Considerations section back to Data Integrity
#410
w3cbot
opened
10 months ago
0
Highlight security/privacy trade-offs between RDF-CANON and JCS
#409
w3cbot
opened
10 months ago
0
Add guidance on inclusion of unique tracking identifiers
#408
w3cbot
opened
10 months ago
0
Add guidance for wallets when using JsonSchemaCredential and selected disclosure
#407
w3cbot
opened
10 months ago
0
Encourage usage of OHTTP during schema resolution
#406
w3cbot
opened
10 months ago
0
Address Metadata-Driven Correlation
#405
w3cbot
closed
4 months ago
1
Address Metadata-Driven Correlation
#404
w3cbot
opened
10 months ago
0
Mitigating Location Correlation via Common Issuers
#403
w3cbot
closed
4 months ago
1
Mitigating Location Correlation via Common Issuers
#402
w3cbot
opened
10 months ago
0
Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing
#401
w3cbot
closed
4 months ago
1
Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing
#400
w3cbot
opened
10 months ago
0
Addressing Verifier Stored Data Vulnerabilities and Legal Compliance
#399
w3cbot
closed
4 months ago
1
Addressing Verifier Stored Data Vulnerabilities and Legal Compliance
#398
w3cbot
opened
10 months ago
0
Flesh out Privacy Considerations based on RDF Concepts text.
#396
w3cbot
opened
11 months ago
0
Flesh out Privacy Considerations based on RDf Concepts text.
#395
w3cbot
opened
11 months ago
0
Flesh out Privacy Considerations based on RDF Concepts text.
#394
w3cbot
opened
11 months ago
0
Fleshes out Privacy Considerations based on RDF Concepts text.
#393
w3cbot
opened
11 months ago
0
Fleshes out Privacy Considerations based on RDF Concepts text.
#392
w3cbot
opened
11 months ago
0
Security and Privacy Self-Review Questionnaire
#391
w3cbot
opened
11 months ago
0
Adds Privacy Considerations for RDF.
#390
w3cbot
opened
12 months ago
0
Security and Privacy Self-Review Questionnaire
#389
w3cbot
opened
1 year ago
0
Privacy Working Group
#388
w3cbot
opened
1 year ago
0
Privacy should be mitigated, not just detailed
#387
w3cbot
opened
1 year ago
0
Align exposing `scalabilityMode` with the WebRTC "hardware capabilities" check
#386
w3cbot
opened
1 year ago
0
"Performance APIs, security and privacy" document
#385
w3cbot
opened
1 year ago
0
The charter should discuss open issues around privacy
#384
w3cbot
opened
1 year ago
0
Compute Pressure Specification Review
#383
w3cbot
opened
1 year ago
0
Eligibility for autofill
#382
w3cbot
opened
1 year ago
0
[PING] Only allow triggering authentication from a foreground tab
#381
w3cbot
opened
1 year ago
0
Move privacy and security considerations to a separate section
#380
w3cbot
opened
1 year ago
0
Read-only events should require authentication
#379
w3cbot
opened
1 year ago
0
How can clients verify that a device they're interacting with is compliant?
#378
w3cbot
opened
1 year ago
0
Specify what kind of attacks are considered and addressed
#377
w3cbot
opened
1 year ago
0
"no side channels" subsection issues
#376
w3cbot
opened
1 year ago
0
"first party context" section concerns
#375
w3cbot
opened
1 year ago
0
isExtended is additional fingerprinting surface
#374
w3cbot
closed
4 months ago
1
Screen labels seem especially privacy risking and identifying
#373
w3cbot
closed
4 months ago
1
Security considerations section links to non-versioned GH doc
#372
w3cbot
closed
4 months ago
1
Move existing methods of inferring multi-montior support behind permission
#371
w3cbot
closed
4 months ago
1
"User notifications" section should be more specific
#370
w3cbot
opened
1 year ago
0
"power-supply" is a fingerprinting vector
#369
w3cbot
opened
1 year ago
0
Text and clarity issues in the security and privacy considerations section
#368
w3cbot
opened
1 year ago
0
Feature can be abused to create cross-site covert channels
#367
w3cbot
opened
1 year ago
0
Privacy Considerations section should be expanded to cover risks deriving from cross-origin communication channels
#366
w3cbot
opened
1 year ago
0
"sideloading" and "untrustworthy" references are unclear given lack of authentication and integrity
#365
w3cbot
opened
1 year ago
0
VideoDecoder API may expose the underlying buffer pool size
#364
w3cbot
opened
1 year ago
0
Spec should document fingerprinting and XSLeak risk
#363
w3cbot
opened
1 year ago
0
notifying the site of a browser intervention can be user harming
#362
w3cbot
opened
1 year ago
0
Previous
Next