moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-23 01:32:22 -05:00
Code Issues Releases Wiki Activity

XEP-0450: Release version 0.3.2

Browse Source 
Use 'distrusted' consistently
This commit is contained in:
Melvin Keskin 2021-06-27 13:20:17 +02:00
parent 27763c3d70
commit 17e384071e
No known key found for this signature in database
GPG Key ID: 04EFAD0F7A4D9724
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xep-0450.xml
View File

@ -37,6 +37,12 @@
<email>melvo@olomono.de</email>
<jid>melvo@olomono.de</jid>
</author>
<revision>
<version>0.3.2</version>
<date>2021-06-27</date>
<initials>melvo</initials>
<remark>Use 'distrusted' consistently</remark>
</revision>
<revision>
<version>0.3.1</version>
<date>2021-05-14</date>
@ -473,7 +479,7 @@
<section1 topic='Implementation Notes' anchor='implementation-notes'>
<section2 topic='Storing Trust Message Information from Endpoints with Unauthenticated Keys' anchor='implementation-notes-storing-trust-message-information-unauthenticated-keys'>
<p>
A client MUST save the information of a trust message until the key of the endpoint that sent the trust message is authenticated, so that the key can then be authenticated or revoked.
A client MUST save the information of a trust message until the key of the endpoint that sent the trust message is authenticated, so that the key can then be authenticated or distrusted.
Storing data of a trust message from an endpoint with an unauthenticated key is necessary because the receiving endpoint can only use that data after authenticating the sending endpoint's key and that data might not be received again.
Afterwards the information of the trust message MAY be deleted.
</p>
@ -486,7 +492,7 @@
</section2>
<section2 topic='Storing Trust Message Information for Unknown Keys' anchor='implementation-notes-storing-trust-message-information-unknown-keys'>
<p>
A client MUST save the information of a trust message until it has fetched the corresponding key so that the key can then be authenticated or revoked.
A client MUST save the information of a trust message until it has fetched the corresponding key so that the key can then be authenticated or distrusted.
Afterwards the information of the trust message can be deleted.
</p>
<p>