[Standards] UPDATED: XEP-0384 (OMEMO Encryption)

2021-09-28 Thread XSF Editor
Version 0.8.0 of XEP-0384 (OMEMO Encryption) has been released.

Abstract:
This specification defines a protocol for end-to-end encryption in
one-to-one chats, as well as group chats where each participant may
have multiple clients per account.

Changelog:
Update to XEP-0420 version 0.4.0 and adjust namespace:
* Replace SCE's old 'content' element by its new 'envelope' element
* Replace SCE's old 'payload' element by its new 'content' element
* Update SCE's namespace to 'urn:xmpp:sce:1'
* Update namespace to 'urn:xmpp:omemo:2' (melvo)

URL: https://xmpp.org/extensions/xep-0384.html

Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


[Standards] UPDATED: XEP-0384 (OMEMO Encryption)

2020-10-06 Thread XSF Editor
Version 0.7.0 of XEP-0384 (OMEMO Encryption) has been released.

Abstract:
This specification defines a protocol for end-to-end encryption in
one-to-one chats, as well as group chats where each participant may
have multiple clients per account.

Changelog:
* Various fixes, clarifications and general improvements. (th)

URL: https://xmpp.org/extensions/xep-0384.html

Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


[Standards] UPDATED: XEP-0384 (OMEMO Encryption)

2020-06-09 Thread XSF Editor
Version 0.6.0 of XEP-0384 (OMEMO Encryption) has been released.

Abstract:
This specification defines a protocol for end-to-end encryption in
one-to-one chats, as well as group chats where each participant may
have multiple clients per account.

Changelog:
Incorporate feedback around cryptographic terms and content by Sofía
Celi. (ps)

URL: https://xmpp.org/extensions/xep-0384.html

Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


[Standards] UPDATED: XEP-0384 (OMEMO Encryption)

2020-03-30 Thread pep
Version 0.5.0 of XEP-0384 (OMEMO Encryption) has been released.

Abstract:
This specification defines a protocol for end-to-end encryption in
one-to-one chats, as well as group chats where each participant may
have multiple clients per account.

Changelog:
* Usage of Ed25519 public keys, made XEdDSA optional.
* Threat model added. (th)

URL: https://xmpp.org/extensions/xep-0384.html

Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] UPDATED: XEP-0384 (OMEMO Encryption)

2020-03-10 Thread syndace
Which "extra robustness" are you talking about? GCM is not meant to handle larger amounts of data. Also the Double Ratchet protocol uses CBC internally, so this reduces the number of separate crypto primitives we need.

 
 

Gesendet: Dienstag, 10. März 2020 um 16:38 Uhr
Von: "Thilo Molitor" 
An: "XMPP Standards" 
Betreff: Re: [Standards] UPDATED: XEP-0384 (OMEMO Encryption)




>* Use AES256/CBC to encrypt SCE payload.
Why use CBC and not GCM for extra robustness?

- tmolitor

___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___



___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] UPDATED: XEP-0384 (OMEMO Encryption)

2020-03-10 Thread Thilo Molitor




>* Use AES256/CBC to encrypt SCE payload.
Why use CBC and not GCM for extra robustness?

- tmolitor

___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] UPDATED: XEP-0384 (OMEMO Encryption)

2020-03-10 Thread Maxime Buquet
On 2020/03/10, p...@bouah.net wrote:
> Version 0.4.0 of XEP-0384 (OMEMO Encryption) has been released.
> 
> Abstract:
> This specification defines a protocol for end-to-end encryption in
> one-to-one chats, as well as group chats where each participant may
> have multiple clients per account.
> 
> Changelog:
> * Incorporate the double ratchet protocol specification.
> * Use one node to store all bundles. One item per bundle.
> * Recommend 'open' access model for both PEP nodes.
> * Specify OMEMO encryption for XEP-0045 Multi-User Chats.
> * Use XEP-0420: Stanza Content Encryption.
> * Use AES256/CBC to encrypt SCE payload.
> * Change namespace to

'urn:xmpp:omemo:1'

It seems the script didn't pick on up this. Thanks to those who told me :)

> * Use wrapping 'keys' element for key elements in 'header'.
> * Define threat model (dg)

The XEP is also being moved back to Experimental with this update.

-- 
Maxime “pep” Buquet


signature.asc
Description: PGP signature
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


[Standards] UPDATED: XEP-0384 (OMEMO Encryption)

2020-03-10 Thread pep
Version 0.4.0 of XEP-0384 (OMEMO Encryption) has been released.

Abstract:
This specification defines a protocol for end-to-end encryption in
one-to-one chats, as well as group chats where each participant may
have multiple clients per account.

Changelog:
* Incorporate the double ratchet protocol specification.
* Use one node to store all bundles. One item per bundle.
* Recommend 'open' access model for both PEP nodes.
* Specify OMEMO encryption for XEP-0045 Multi-User Chats.
* Use XEP-0420: Stanza Content Encryption.
* Use AES256/CBC to encrypt SCE payload.
* Change namespace to
* Use wrapping 'keys' element for key elements in 'header'.
* Define threat model (dg)

URL: https://xmpp.org/extensions/xep-0384.html

Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


[Standards] UPDATED: XEP-0384 (OMEMO Encryption)

2017-09-15 Thread XSF Editor
Version 0.2 of XEP-0384 (OMEMO Encryption) has been released.

Abstract:
This specification defines a protocol for end-to-end encryption in
one-on-one chats that may have multiple clients per account.

Changelog:
(see in-document revision history)

URL: https://xmpp.org/extensions/xep-0384.html
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___