Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#78871 - Build libQuotient with encryption
Attached to Project:
Community Packages
Opened by Luna Celeste (luna) - Friday, 23 June 2023, 14:38 GMT
Last edited by Antonio Rojas (arojas) - Friday, 23 June 2023, 17:39 GMT
Opened by Luna Celeste (luna) - Friday, 23 June 2023, 14:38 GMT
Last edited by Antonio Rojas (arojas) - Friday, 23 June 2023, 17:39 GMT
|
DetailsDescription: libQuotient has encryption support as of May 2023. It's an optional feature but can be enabled by defining `Quotient_ENABLE_E2EE` when calling cmake. neochat, which depends on libQuotient, already supports encryption, but needs the library to be built with encryption enabled.
|
This task depends upon
Closed by Antonio Rojas (arojas)
Friday, 23 June 2023, 17:39 GMT
Reason for closing: Won't implement
Friday, 23 June 2023, 17:39 GMT
Reason for closing: Won't implement
https://github.com/quotient-im/libQuotient/blob/dev/CMakeLists.txt#L16
I don't think it's safe to enable such a security critical feature until it's deemed stable by upstream