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

MSC3202: Encrypted appservices #3202

Open
wants to merge 13 commits into
base: old_master
Choose a base branch
from
+158 −0
Open

MSC3202: Encrypted appservices #3202

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
d56527b
Encrypted appservices
turt2live May 18, 2021
efabfe4
Guess number
turt2live May 18, 2021
3f394a8
number
turt2live May 18, 2021
f551ae5
Mention opt-in registration flag
turt2live Nov 3, 2021
4f6e256
Add device_id assertion
turt2live Nov 3, 2021
9001a67
Mention device_id prefixing
turt2live Nov 4, 2021
472226b
Document optimizations
turt2live Nov 24, 2021
937e4c5
Include fallback key support
turt2live Nov 24, 2021
9893a5f
Document appservice transaction retries and handling
turt2live Nov 24, 2021
208decb
Update unstable prefixing
turt2live Nov 24, 2021
e586c39
Merge branch 'old_master' into travis/msc/otk-dl-appservice
turt2live Mar 23, 2023
f875ffe
Fix naming of `device_one_time_key_counts` to match CS API
turt2live Mar 23, 2023
47d2080
Actually, *this* matches the CS API
turt2live Mar 23, 2023
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
Prev Previous commit
Actually, *this* matches the CS API
  • Loading branch information
@turt2live
turt2live committed Mar 23, 2023
commit 47d20802ecb3fb37a96caabe25099413bd853a67
6 changes: 3 additions & 3 deletions proposals/3202-encrypted-appservices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ defining a new set of keys on the appservice `/transactions` endpoint, similar t
"changed": ["@alice:example.org"],
"left": ["@bob:example.com"]
},
"device_one_time_key_counts": {
"device_one_time_keys_count": {
"@_irc_bob:example.org": {
"DEVICEID": {
"curve25519": 10,
Expand All @@ -49,7 +49,7 @@ These fields are heavily inspired by [the extensions to /sync](https://matrix.or
in the client-server API.

All the new fields can be omitted if there are no changes for the appservice to handle. For
`device_one_time_key_counts` and `device_unused_fallback_key_types`, the format is slightly different
`device_one_time_keys_count` and `device_unused_fallback_key_types`, the format is slightly different
from the client-server API to better map the appservice's user namespace users to the counts. Users
in the namespace without keys or which have unchanged keys since the last transaction can be omitted
(more details on this later on). Note that fallback keys are described in
Expand Down Expand Up @@ -141,7 +141,7 @@ all the users in its namespace.
While this MSC is not considered stable for implementation, implementations should use `org.matrix.msc3202.`
as a prefix to the fields on the `/transactions` endpoint. For example:
* `device_lists` becomes `org.matrix.msc3202.device_lists`
* `device_one_time_key_counts` becomes `org.matrix.msc3202.device_one_time_key_counts`
* `device_one_time_keys_count` becomes `org.matrix.msc3202.device_one_time_keys_count`
* `device_unused_fallback_key_types` becomes `org.matrix.msc3202.device_unused_fallback_key_types`

Appservices which support encryption but never see these fields (ie: server is not implementing this in an
Expand Down