wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify that valid_until_ts is in milliseconds, like other timestamps used in Matrix

Browse source 
Signed-off-by: Valentin Lorentz <progval+git@progval.net>
This commit is contained in:
Valentin Lorentz 2022-05-10 19:34:01 +02:00
parent fd2d5b8a49
commit 34589078fd
2 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

1
changelogs/server_server/newsfragments/1055.clarification Normal file
View file

@ -0,0 +1 @@
Clarify that valid_until_ts is in milliseconds, like other timestamps used in Matrix

7
data/api/server-server/definitions/keys.yaml
View file

@ -88,9 +88,10 @@ properties:
type: integer type: integer
format: int64 format: int64
description: |- description: |-
POSIX timestamp when the list of valid keys should be refreshed. This field MUST POSIX timestamp in milliseconds when the list of valid keys should be refreshed.
be ignored in room versions 1, 2, 3, and 4. Keys used beyond this timestamp MUST This field MUST be ignored in room versions 1, 2, 3, and 4. Keys used beyond this
be considered invalid, depending on the [room version specification](/rooms). timestamp MUST be considered invalid, depending on the
[room version specification](/rooms).
Servers MUST use the lesser of this field and 7 days into the future when Servers MUST use the lesser of this field and 7 days into the future when
determining if a key is valid. This is to avoid a situation where an attacker determining if a key is valid. This is to avoid a situation where an attacker