Version 0.6.0 of XEP-0434 (Trust Messages (TM)) has been released.
Abstract:
This document specifies a way to communicate the trust in public long-
term keys used by end-to-end encryption protocols from one endpoint to
another.
Changelog:
Specify key identifier encoding, improve glossary and
Version 0.5.0 of XEP-0434 (Trust Messages (TM)) has been released.
Abstract:
This document specifies a way to communicate the trust in public long-
term keys used by end-to-end encryption protocols from one endpoint to
another.
Changelog:
Update to XEP-0420 version 0.4.0 and adapt namespace to
Version 0.4.0 of XEP-0434 (Trust Messages (TM)) has been released.
Abstract:
This document specifies a way to communicate the trust in public long-
term keys used by end-to-end encryption protocols from one endpoint to
another.
Changelog:
Add new section, use more precise sentences, apply
Version 0.3.0 of XEP-0434 (Trust Messages (TM)) has been released.
Abstract:
This document specifies a way to communicate the trust in public long-
term keys used by end-to-end encryption protocols from one endpoint to
another.
Changelog:
Clarify usage, use real namespace for examples and add
I am surprised to find that this XEP does not specify the format of the
key identifier anywhere (at least I couldn't find it).
I had expected to find that the key identifier is qualified by the
encryption scheme of the key. That is, instead of
Here is an extensive and detailed example to show the usefulness of TM
/ ATM and hopefully answer your question. To keep it simple,
implementation details are omitted.
# Baseline
Alice would like to chat end-to-end encrypted with Bob. She uses a
notebook, a tablet and a smartphone for chatting
I mean, what 'remaining authentications' are you referring to?
Can you describe a scenario, like, Romeo with a smartphone and Juliet with
desktop computer want to initiate an encrypted chat, what do they do?
On Mon, Dec 7, 2020, 00:00 Melvin Keskin wrote:
> Hello Andrew,
>
> thanks for your
Hello Andrew,
thanks for your questions!
The authentication of public long-term keys is needed to ensure that
those keys are the keys of the pretended owners.
Trust Messages (TM) is intended to provide a basis for XEPs such as
Automatic Trust Management (ATM) (
Can someone explain this to me like I'm 5 years old? Why is this
needed and how it improves security over regular 0384? Isn't
fingerprint matching enough a caution?
вт, 1 дек. 2020 г. в 22:37, Jonas Schäfer :
>
> Version 0.2.0 of XEP-0434 (Trust Messages (TM)) has been released.
>
> Abstract:
>
Version 0.2.0 of XEP-0434 (Trust Messages (TM)) has been released.
Abstract:
This document specifies a way to communicate the trust in public long-
term keys used by end-to-end encryption protocols from one endpoint to
another.
Changelog:
Improve explanations, descriptions and examples,
10 matches
Mail list logo