Create client hint mapping rows for CheckUser-worthy events
Closed, ResolvedPublic
Actions

Description

In T337944: Implement support for requesting client hint header we added support for setting the Accept-CH header on the following workflows:

[web] Special:CreateAccount
[web] Special:UserLogin
[web] Special:UserLogout
[web] Special:PasswordReset
[web] Special:EmailUser
[web] ?action=history (for rollback)
[API] edit handled via postEdit mw.hook (as is non-API editing)

In T258105: Implement storage for User-Agent Client Hints header data we defined database tables to store the data. Currently, editing scenarios write data to these tables (using the postEdit mw.hook).

We need to create record client hint data for:

Related Objects
Search...

View Standalone Graph

This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Status	Subtype	Assigned	Task
			· · ·
Resolved		kostajh	T257893 [EPIC] Support User-Agent Client Hints header in CheckUser
Resolved		kostajh	T341094 Create client hint mapping rows for CheckUser-worthy events
Resolved	Feature	Dreamy_Jazz	T324907 Create separate tables for log events in CheckUser
Resolved		Dreamy_Jazz	T345818 Store client hint mapping rows for login events
Open		kostajh	T345819 Store client hint mapping rows for logout events
Resolved		Dreamy_Jazz	T345820 Store client hint mapping rows for password reset events
Resolved		Dreamy_Jazz	T345821 Store client hint mapping rows for email user events
Open		Dreamy_Jazz	T347393 Store client hint mapping rows for user account creations on loginwiki
Open		kostajh	T345817 Store client hint mapping rows for user account creation events
			· · ·

Event Timeline

kostajh created this task.Jul 4 2023, 7:20 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 4 2023, 7:20 PM

We could either mark this task as stalled pending the resolution of T258105: Implement storage for User-Agent Client Hints header data, or, we can start building on top of the WIP patch for DB storage.

Dreamy_Jazz added a project: CheckUser.Jul 4 2023, 10:38 PM

Dreamy_Jazz added a subtask: T324907: Create separate tables for log events in CheckUser.Jul 13 2023, 7:32 PM

Actions which produce a public log entry will need to wait for T324907 to be complete (so that the client hints data can be stored under the log ID).

For events which do not have a log ID or revision ID, they will also need to wait for T324907 to be complete as it will reference a row in cu_private_event.

Dreamy_Jazz mentioned this in T341093: Provide public explanation of how and why we make use of high entropy user-agent client hints.Jul 21 2023, 2:53 PM

Dreamy_Jazz moved this task from Untriaged to CheckUser on the Anti-Harassment board.Jul 22 2023, 5:47 PM

In T341094#9021211, @Dreamy_Jazz wrote:

Actions which produce a public log entry will need to wait for T324907 to be complete (so that the client hints data can be stored under the log ID).

For events which do not have a log ID or revision ID, they will also need to wait for T324907 to be complete as it will reference a row in cu_private_event.

Marking as stalled pending T324907: Create separate tables for log events in CheckUser.

Dreamy_Jazz updated the task description. (Show Details)Aug 23 2023, 4:21 PM

Dreamy_Jazz updated the task description. (Show Details)