Commit graph

5234 commits

Author SHA1 Message Date
Andrew Morgan b26a9ed1fd Expand on why we can't trust dirty homeservers 2019-07-23 13:28:42 +01:00
Andrew Morgan 577021f12b resolve some comments 2019-07-23 11:48:01 +01:00
Luca Becker d43111cdd2
Incorporated @turt2live suggestions.
Used **Note** to describe notes around the authorisation rules. Otherwise restored the original state for the consequences from the auth rules.
Moved the clarification regarding default power levels up above the auth rules. Removed third sentence. And followed @turt2live's example, but opted for "for users in that room" because the default user power level is applied to all users.
2019-07-23 11:25:34 +02:00
Richard van der Hoff 9e264fedc9 Updates
* preserve *all* of `create`
* don't preserve `notifications` or `algorithm`, and add some justifcation.
2019-07-22 16:47:49 +01:00
Andrew Morgan 887cd5e7d0 I really hope someone doesn't invest none-hash 2019-07-22 16:00:29 +01:00
Andrew Morgan 0444c8016b review comments 2019-07-22 15:33:49 +01:00
Richard van der Hoff 4503327450 Add some compatibility hacks. 2019-07-22 15:17:52 +01:00
Luca Becker 094005dca1
Incorporated @turt2live suggestions.
Added missing added and removed to the rule, because these keys are not required for m.room.power_levels. Also moved the note down to the Note section.
2019-07-18 08:55:58 +02:00
Luca Becker 8aece4f644
Incorporated @richvdh suggestions 2019-07-17 23:26:10 +02:00
Richard van der Hoff d324cac847 preserve powerlevel 2019-07-16 19:32:34 +01:00
Richard van der Hoff b49a950245
Update proposals/2176-update-redaction-rules.md
fix typo

Co-Authored-By: Kitsune Ral <Kitsune-Ral@users.sf.net>
2019-07-16 19:26:02 +01:00
Luca Becker 15994c61a5
Clarification regarding authorisation rules
The rules for m.room.power_levels power were somewhat unclear regarding the behaviour towards the always present keys, such as kick and ban. Additionally, it is now also clarified that in the users and events dictionary also added and removed keys are taken into consideration.
2019-07-16 17:33:13 +02:00
Sorunome 9ebcff5758
fix typo, add section on html details element 2019-07-16 17:11:07 +02:00
Andrew Morgan 36cb8ed894 none -> m.none 2019-07-16 10:44:02 +01:00
Sorunome 1f786ae6dc
commit image into repo, fix typo 2019-07-15 20:52:24 +02:00
David Baker d9269b084f Exclude pubkey endpoints from auth 2019-07-15 16:58:24 +01:00
David Baker a1de6ff634 Hopefully clarify some bits 2019-07-15 10:26:24 +01:00
Richard van der Hoff cd5549d483 Proposal to update the redaction algorithm 2019-07-14 22:50:46 +01:00
Richard van der Hoff b09d48a9f7 Spec link 2019-07-14 20:22:39 +01:00
Richard van der Hoff 78d46b2890 Proposal to move the redacts key to a sane place 2019-07-14 20:20:09 +01:00
David Baker 25a47afa32
unnecessary capital mk. 2
Co-Authored-By: J. Ryan Stinnett <jryans@gmail.com>
2019-07-12 11:55:40 +01:00
David Baker 6e061b1baf
unnecessary capital
Co-Authored-By: J. Ryan Stinnett <jryans@gmail.com>
2019-07-12 11:55:11 +01:00
David Baker f474b31f5f
typo
Co-Authored-By: J. Ryan Stinnett <jryans@gmail.com>
2019-07-12 11:54:45 +01:00
Andrew Morgan 3514437d24 Ability for client/server to decide on no hashing 2019-07-12 11:37:41 +01:00
David Baker 9bb6ad80d1 typo 2019-07-10 16:13:38 +01:00
Travis Ralston 7b0f5ea77b
Merge pull request #2159 from jimmycuadra/reference-hash-purpose
Clarify the purpose of reference hashes.
2019-07-09 16:27:44 -06:00
Jimmy Cuadra a3d2d14dae Rephrase explanation of the purpose of reference hashes and link to the
room version spec.

Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com>
2019-07-09 15:26:03 -07:00
Andrew Morgan 52643a92c6
Less confusing wording on Application Service's Legacy Routes (#2160)
https://matrix.org/docs/spec/application_service/r0.1.1#legacy-routes

The "becomes" wording made it a little bit confusing for which was the new route and which was the old.
2019-07-09 17:54:45 +01:00
Jimmy Cuadra 5df86dabe0 Clarify the purpose of reference hashes.
The server-server specification describes a "reference hash" of an event
and how to calculate it, but is otherwise not mentioned anywhere else in
the document. This change adds a sentence to explain that they are used
for event identifiers in later room versions, which are described in
other documents.

Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com>
2019-07-09 01:14:29 -07:00
Hubert Chathi ee04b778cf
Merge pull request #2157 from a-andreyev/aa13q/api-client-server-device-keys
Client-server: Fix upload keys example request
2019-07-08 15:57:56 -04:00
Alexey Andreyev 9ed19a37ad
Client-server: Fix upload keys example request
Contributes to #1733

Signed-off-by: Alexey Andreyev <aa13q@ya.ru>
2019-07-08 22:28:32 +03:00
Andrew Morgan ed67e26037 pepper must not be an empty string, append medium 2019-07-08 17:03:20 +01:00
Andrew Morgan 1963a24832 fix attacks paragraph 2019-07-08 13:27:38 +01:00
Andrew Morgan dd8a6549c9 Address review comments 2019-07-08 11:55:37 +01:00
David Baker 701d340da1 Remove exception for request/submitToken 2019-07-05 19:00:15 +01:00
David Baker bf8a1e5d5f Add way to get the HS to bind/unbind existing 3pids 2019-07-05 18:11:42 +01:00
Andrew Morgan 3702669424 update from comments 2019-07-05 15:59:29 +01:00
David Baker 30dcc28f9b try & clarify that HS signature isn't the only acceptable auth for unbind 2019-07-04 18:38:31 +01:00
Andrew Morgan f4a1e02884 simple method once more 2019-07-04 16:28:49 +01:00
Hubert Chathi 4d31ddc8c9 additions and clarifications
- indicate how to use MSC 1946 to store/share private keys
- add signing by devices to enable migrating from device verifications
- add information about signature upload failures and M_INVALID_SIGNATURE code
- add security consideration
2019-07-03 15:09:06 -04:00
Travis Ralston db5ce0c69e
Merge pull request #2152 from matrix-org/jryans/room-one-to-one-push-rule
Clarify `.m.rule.room_one_to_one` push rule
2019-07-03 09:35:12 -06:00
J. Ryan Stinnett 9208c5cd13 Add changelog 2019-07-03 11:34:00 +01:00
J. Ryan Stinnett 4c65660b96 Clarify .m.rule.room_one_to_one push rule
This clarifies the `.m.rule.room_one_to_one` push rule by adding a condition on
event type. Some parts of the spec already had this info, while others were
missing it. Synapse has had this behaviour since the push rule appeared.

Fixes https://github.com/matrix-org/matrix-doc/issues/2150
2019-07-03 10:59:38 +01:00
reivilibre 8033ab1c86 Fix Push Gateway API example: Field renamed to event_id
I believe this was forgotten in:
71cb646541
2019-07-03 10:36:16 +01:00
Andrew Morgan 53bd384f2e Clarify salting 2019-07-03 09:59:38 +01:00
Hubert Chathi 3aaf181db2 rename some things and add clarification 2019-07-02 14:05:06 -04:00
David Baker 1a669348d8 http status code 2019-07-02 11:27:46 +01:00
David Baker d15c9df115
fullstop
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-07-02 11:25:26 +01:00
David Baker e28f7aad72
slash
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-07-02 11:25:12 +01:00
David Baker 4c72c37b80
slash
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-07-02 11:24:51 +01:00