Re: [w3c/uievents-code] Tasks for wide review (Issue #35)

# Privacy / Security self-review

2.1 What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?
This spec defines a set of valid values for the `code` attribute of the various key events. This is necessary for sites that need to identify the position of the key that is being pressed (for example, WASD keys for games), in a way that supports different keyboard layouts.

2.2 Do features in your specification expose the minimum amount of information necessary to enable their intended uses?
Yes

2.3 How do the features in your specification deal with personal information, personally-identifiable information (PII), or information derived from them?
N/A

2.4 How do the features in your specification deal with sensitive information?
N/A

2.5 Do the features in your specification introduce new state for an origin that persists across browsing sessions?
No

2.6 Do the features in your specification expose information about the underlying platform to origins?
There are a few special `code` values that can be used to identify particular keyboards. For example, `IntlBackslash`, `IntlRo` and `IntlYen`. The user would have to type these keys for the information to be exposed.

2.7 Does this specification allow an origin to send data to the underlying platform?
No

2.8 Do features in this specification enable access to device sensors?
No

2.9 Do features in this specification enable new script execution/loading mechanisms?
No

2.10 Do features in this specification allow an origin to access other devices?
No

2.11 Do features in this specification allow an origin some measure of control over a user agent’s native UI?
No

2.12 What temporary identifiers do the features in this specification create or expose to the web?
None

2.13 How does this specification distinguish between behavior in first-party and third-party contexts?
No difference

2.14 How do the features in this specification work in the context of a browser’s Private Browsing or Incognito mode?
No difference from normal behavior

2.15 Does this specification have both "Security Considerations" and "Privacy Considerations" sections?
Yep!

2.16 Do features in your specification enable origins to downgrade default security protections?
Nope

2.17 How does your feature handle non-"fully active" documents?
This attribute is only associated with key events, which are only sent if the document is fully active.

2.18 What should this questionnaire have asked?
???

3.1 Passive Network Attackers
N/A. These are values for a static attribute on an event.

3.2. Active Network Attackers
N/A

3.3. Same-Origin Policy Violations
N/A

3.4 Third-Party Tracking
N/A

3.5 Legitimate Misuse
A site could capture all keypresses and build a map of the values generated by the keyboard. If the user types enough any of the special keys are are only present on certain keyboards, then the site could try to match those values against a database of known keyboard layouts to narrow down the possible keyboard being used.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents-code/issues/35#issuecomment-1301310761

You are receiving this because you are subscribed to this thread.

Message ID: <w3c/uievents-code/issues/35/1301310761@github.com>