Accepting request 1044003 from home:Dead_Mozay:matrix

- Update to version 0.7.0:
  * E2EE is the biggest part of this release, 
    + The following parts of E2EE are known to work:
      - foundations additional contributions and refactoring.
      - Olm/Megolm signalling with our parties/devices.
      - managing device and one-time keys.
      - sending and receiving (monstrous new encrypted messages.
      - encrypting/decrypting attachment.
      - retrieval and decryption of historical messages keys 
        for which are already in the database.
      - device verification.
    + What is not there yet:
      - historical Megolm sessions are not requested from other 
        devices/parties, so you will see quite a few undecryptable
        messages in rooms with past communication - this might be 
        fixed (if possible without breaking the API) in further 
        0.7.x releases.
      - secure server-side storage (SSSS) is not supported at 
        all for now, and will likely require API breakage so 
        will come in 0.8.
      - soft logout is not supported; this is also a subject of 0.8.
    + Because there's no soft logout the database for a given account 
      is completely reset upon a successful login attempt. This may 
      come as a very unpleasant surprise if you don't keep your 
      login session between client restarts; but this is a necessary
      trade-off for the current feature set (see #546 for the 
      discussion). Together with the rest of the above not-there-yet
      list, this means that you MUST NOT use E2EE with 
      libQuotient-backed clients as your only device(s) on 
      the account - there's quite a risk of losing encrypted
      conversations if anything happens to the database libQuotient
      keeps key material in, or if you lose your session and have
      to log in again. Did I mention the whole E2EE functionality
      is still in beta? Client authors are strongly recommended 
      to show big scary warnings against E2EE for now.
  * Read markers -> read receipts + fully read markers.

OBS-URL: https://build.opensuse.org/request/show/1044003
OBS-URL: https://build.opensuse.org/package/show/network:messaging:matrix/libQuotient?expand=0&rev=20
This commit is contained in:
Dead Mozay 2022-12-21 05:26:59 +00:00 committed by Git OBS Bridge
parent 870d8e8977
commit edfa87baaf
4 changed files with 54 additions and 11 deletions

View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:12b15d1296e630477d5e8f4d32c821dc724b3c5b99d15d383417ba7d88f03c46
size 562144

3
libQuotient-0.7.0.tar.gz Normal file
View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:2e46a9889c2ce86b780f04b0b831896179af6621177f805c1a650a980e041525
size 667312

View File

@ -1,3 +1,43 @@
-------------------------------------------------------------------
Wed Dec 21 04:58:08 UTC 2022 - Dead Mozay <dead_mozay@opensuse.org>
- Update to version 0.7.0:
* E2EE is the biggest part of this release,
+ The following parts of E2EE are known to work:
- foundations additional contributions and refactoring.
- Olm/Megolm signalling with our parties/devices.
- managing device and one-time keys.
- sending and receiving (monstrous new encrypted messages.
- encrypting/decrypting attachment.
- retrieval and decryption of historical messages keys
for which are already in the database.
- device verification.
+ What is not there yet:
- historical Megolm sessions are not requested from other
devices/parties, so you will see quite a few undecryptable
messages in rooms with past communication - this might be
fixed (if possible without breaking the API) in further
0.7.x releases.
- secure server-side storage (SSSS) is not supported at
all for now, and will likely require API breakage so
will come in 0.8.
- soft logout is not supported; this is also a subject of 0.8.
+ Because there's no soft logout the database for a given account
is completely reset upon a successful login attempt. This may
come as a very unpleasant surprise if you don't keep your
login session between client restarts; but this is a necessary
trade-off for the current feature set (see #546 for the
discussion). Together with the rest of the above not-there-yet
list, this means that you MUST NOT use E2EE with
libQuotient-backed clients as your only device(s) on
the account - there's quite a risk of losing encrypted
conversations if anything happens to the database libQuotient
keeps key material in, or if you lose your session and have
to log in again. Did I mention the whole E2EE functionality
is still in beta? Client authors are strongly recommended
to show big scary warnings against E2EE for now.
* Read markers -> read receipts + fully read markers.
-------------------------------------------------------------------
Thu Oct 7 08:37:12 UTC 2021 - Dead Mozay <dead_mozay@opensuse.org>

View File

@ -1,7 +1,7 @@
#
# spec file for package libQuotient
#
# Copyright (c) 2021 SUSE LLC
# Copyright (c) 2022 SUSE LLC
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@ -16,11 +16,11 @@
#
%define soversion 0_6
%define sonum 0.6
%define soversion 0_7
%define sonum 0.7
%bcond_with e2ee
Name: libQuotient
Version: 0.6.11
Version: 0.7.0
Release: 0
Summary: Library for Qt Matrix Clients
License: LGPL-2.1-only
@ -30,10 +30,13 @@ Source0: https://github.com/quotient-im/%{name}/archive/%{version}/%{name
BuildRequires: cmake
BuildRequires: gcc-c++
BuildRequires: pkgconfig
BuildRequires: pkgconfig(Qt5Core) >= 5.9
BuildRequires: pkgconfig(Qt5Gui)
BuildRequires: pkgconfig(Qt5Multimedia)
BuildRequires: pkgconfig(Qt5Network)
BuildRequires: cmake(Qt5Concurrent)
BuildRequires: cmake(Qt5Core) >= 5.9
BuildRequires: cmake(Qt5DBus)
BuildRequires: cmake(Qt5Gui)
BuildRequires: cmake(Qt5Keychain)
BuildRequires: cmake(Qt5Multimedia)
BuildRequires: cmake(Qt5Network)
%if %{with e2ee}
BuildRequires: cmake(Olm)
%endif