Commit graph

4262 commits

Author SHA1 Message Date
David Baker 2d11217d4e
Typo
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-07-02 10:56:32 +01:00
David Baker 8af35be13f
Typo
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-07-02 10:56:12 +01:00
David Baker fe14d3c9f0 Spec terms response 2019-06-28 18:07:24 +01:00
David Baker 786d5bc281 rewrite UI auth tradeoffs 2019-06-28 10:25:24 +01:00
David Baker 45d630951c back to M_TERMS_NOT_SIGNED 2019-06-28 09:32:15 +01:00
David Baker 83bb3861ba line wrap 2019-06-28 09:31:53 +01:00
David Baker 4be283ccb3
Typing
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-06-27 17:31:15 +01:00
David Baker f95197b422 make the many-anded sentence a list 2019-06-27 17:30:36 +01:00
David Baker 10a6a59a12 Deprecate bind_email / bind_msisdn 2019-06-27 16:58:22 +01:00
David Baker b5326de1c4 Exclude requestToken endpoints from auth requirement 2019-06-27 16:34:46 +01:00
David Baker 21b9eaf8de No custom HTTP headers
Use the obvious way: in the same place as the ID server address
2019-06-26 17:56:41 +01:00
David Baker 2694bb1090 Add really horrible custom HTTP header
for giving the IS token to the HS
2019-06-26 17:41:21 +01:00
David Baker 58cf083a6a backwards compat 2019-06-26 15:31:11 +01:00
David Baker 6273868323 Clarify v1 API deprecation 2019-06-26 15:29:24 +01:00
David Baker 4edf826c93 Capitalise on our identifiers 2019-06-26 15:29:23 +01:00
David Baker ba7047ce77
Clarify we must be accepting HS auth
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-06-26 14:51:11 +01:00
David Baker 1d75828c71 Clarify what to do if no (new) docs 2019-06-26 14:45:25 +01:00
David Baker af691b5a8a
Clarify this applies to 2134
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-06-26 14:37:06 +01:00
David Baker 57094276ce
Typing hard is
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-06-26 14:36:15 +01:00
David Baker 9e0d8b9cb2 Use M_CONSENT_NOT_GIVEN
No idea where I got the other one from: we already have one in the
spec, so use it.
2019-06-25 17:17:39 +01:00
David Baker 0dae2d5812 GET terms must be unauthed.
Detail process for new auth (don't register until consent given).

Specifically mention the authentication header.
2019-06-25 15:52:55 +01:00
David Baker 6f374dc981 Re-write for OpenID auth 2019-06-25 14:58:15 +01:00
David Baker 2c09580e27 line wrap 2019-06-25 11:14:35 +01:00
David Baker abb407145a HS docs must be added too
also, unbind must not error when called by HSes and proxy terms token
2019-06-24 15:30:19 +01:00
David Baker 8ae47557c9 s/Third Party/Accepted/ 2019-06-24 15:22:19 +01:00
David Baker 2555801458 m.third_party_terms -> m.accepted_terms
as it will have the HS's terms too
2019-06-24 14:56:48 +01:00
David Baker 4ba9b2a599 perfix 2019-06-24 13:18:41 +01:00
David Baker a63e4420eb
Linkify
Co-Authored-By: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
2019-06-24 13:17:58 +01:00
David Baker 9ca3ccc81c Add requirments section for de-duping between services. 2019-06-21 09:35:26 +01:00
David Baker d4ca0c237a Specify ID grammar and add comma 2019-06-21 09:25:16 +01:00
David Baker 276e2b6843
Typo
Co-Authored-By: Travis Ralston <travpc@gmail.com>
2019-06-21 09:14:24 +01:00
David Baker cf48030d1f One more tradeoff 2019-06-20 17:48:21 +01:00
David Baker 32c7fc638d you have a number now 2019-06-20 17:44:28 +01:00
David Baker 23af87e9fc Proposal for IS & IM TOS API 2019-06-20 17:41:19 +01:00
Travis Ralston ace94f02b7
Merge pull request #2132 from jimmycuadra/clarify-m.key.verification.start
Clarify the distinction between *m.key.verification.start* and its *m.sas.v1* variant.
2019-06-18 18:42:23 -06:00
Jimmy Cuadra 8246383330 Fix typos in changelog entry. 2019-06-18 16:37:37 -07:00
Travis Ralston 204601d9a4
Merge pull request #2133 from matrix-org/travis/fix-olm-2
Fix link to Olm signing specification
2019-06-18 10:01:04 -06:00
Travis Ralston ffdd8dfe01
Merge pull request #2137 from matrix-org/identity_service/release-r0.2.1
Identity r0.2.1
2019-06-18 08:52:33 -06:00
Travis Ralston d09af5b191 Identity r0.2.1 2019-06-17 11:18:24 -06:00
Travis Ralston 954a5607c3
Merge pull request #2136 from ma1uta/master
Fix typo.
2019-06-17 00:12:39 -06:00
Travis Ralston c63b5aff69
Create 2136.clarification 2019-06-17 00:10:59 -06:00
Anatoly Sablin 802b90d113 Typo. 2019-06-16 22:24:06 +03:00
Jimmy Cuadra 8affb23e5e Address feedback from code review.
* Switch "an SAS" back to "a SAS"
* Remove the `next_method` field from m.key.verification.start$m.sas.v1
  but add additional clarification to its description on
  m.key.verification.start that it is never present for methods that
  verify keys both ways.
2019-06-15 13:44:58 -07:00
Travis Ralston 6f460ad70a minus spec
according to the apache .htaccess we use
2019-06-14 22:26:29 -06:00
Travis Ralston 33ca891e71 Fix link to Olm signing specification
See https://github.com/matrix-org/matrix.org/issues/478
2019-06-14 22:22:43 -06:00
Jimmy Cuadra 5384b61d95 Fix style issues brought up during code review.
Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com>
2019-06-14 17:35:39 -07:00
Jimmy Cuadra bc71dacaf4 Clarify the distinction between *m.key.verification.start* and its *m.sas.v1* variant.
Currently the *m.key.verification.start* event appears twice with the
exact same title, in the "Key verification framework" section and the
"Short Authentication (SAS) verification" section. It's not immediately
clear that the first occurrence describes the format of the event in
general terms and that the second occurrence describes the fields when
the *m.sas.v1* verification method is being used. This is a similar
relationship to the *m.room.message* event and its various *msgtype*
variants.

This commit does three things:

* It tweaks the generation of the documentation to change the title
  of the second occurrence of *m.key.verification.start* to
  distinguish it from the first.
* It updates the language in the description of the two versions of the
  event to better describe the relationship between the two.
* It adds the optional `next_method` field to the schema of the
  *m.sas.v1* variant, as specified in the general form of
  *m.key.verification.start*.

Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com>
2019-06-14 16:20:51 -07:00
Travis Ralston b807e1cbe5
Merge pull request #2129 from jimmycuadra/conditionally-required-url-fields
Remove the "required" designation from the `url` field of certain m.room.message msgtypes.
2019-06-14 14:58:57 -06:00
Matthew Hodgson aadf1cc733
Merge pull request #2131 from jimmycuadra/e2ee-easier-typo
Fix typo in key verification framework section.
2019-06-14 21:56:29 +01:00
Jimmy Cuadra b885714d94 Remove the "required" designation from the url field of certain
m.room.message msgtypes.

Now that content referenced by the *m.audio*, *m.file*, *m.image*, and
*m.video* message types can be encrypted, the `url` field is required
*only* if the content is unencrypted. The "required" designation in the
event schemas (which prefixes the field description with "Required" in
bold in the generated HTML) is used to indicate fields which must always
be present, and this is no longer the case.

Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com>
2019-06-14 13:49:14 -07:00