Skip to content
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

Jump to bottom

matrix_client_information: opt in and security considerations #661

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

matrix_client_information: opt in and security considerations #661

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion spec/matrix_client_information.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,8 @@ All properties are strings. `url` property is optional.

## Client advisory

Storage of client information should be opt-in.

When starting the client after login or update:
1. Upsert an account data event with the type `io.element.matrix_client_information.<device_id>` for the current device

Expand All @@ -45,7 +47,9 @@ Pruning of events depends on implementation of [MSC3391: Removing account
data](https://github.com/matrix-org/matrix-spec-proposals/pull/3391)

## Security considerations
N/A
Storage of client information in account_data exposes information about user sessions to server administrators.
The goal of the feature is to make session management easier, particularly identification of suspicious sessions.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The goal of the feature is to make session management easier, particularly identification of suspicious sessions.
The goal of the feature is to make session management easier, particularly identifying suspicious sessions.

For this reason client information events will not use secret storage.

## Implementations

Expand Down