Created attachment 268359 [details] v0 Use databases/sqlcipher port instead of bundled, which allows removing USES=ssl. Only sqlcipher itself links with OpenSSL, flare's TLS support comes from the rustls crates which is a separate implementation. Have been dogfooding without runtime collisions.
(In reply to Charlie Li from comment #0) Hi, Thanks for your submission. That improvement seems great. Unfortunately, v0.18.4 doesn't seem to work for me (even without your patch): ``` $ flare No such file or directory 2026-02-26 18:54:53.569: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 [2026-02-26T15:54:54Z ERROR presage::manager::registered] failed to set account attributes, this is problematic and should never happen! error=libsignal-service error: Unexpected response: HTTP 422 [2026-02-26T15:54:54Z ERROR flare::backend::manager_thread] Message stream finished. Restarting command loop. [2026-02-26T15:54:55Z ERROR presage::manager::registered] failed to set account attributes, this is problematic and should never happen! error=libsignal-service error: Unexpected response: HTTP 422 [2026-02-26T15:54:55Z ERROR flare::backend::manager_thread] Message stream finished. Restarting command loop. ``` Also there seems to be a error related to sqlcipher. Do you also have this message on your setup? I wonder if it would affect how things work. I tried current port version with your sql change, and it seems to output that sqlcipher_mlock message more times. I tried sending a message and it seems to be 'Sent'. ``` $ flare No such file or directory 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.463: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.630: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.631: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 2026-02-26 21:23:37.631: ERROR MEMORY sqlcipher_mlock: mlock() returned -1 errno=12 ``` So something seems problematic in the new version. I think I will need to contact upstream on GitLab to report this problem. Thank you.
I don't have any of these error messages, at least not with a pre-existing link. Maybe the errors are from a new link? I remember it took about two tries on a new link to populate all the group chats regardless of the sqlcipher interaction.
(In reply to Charlie Li from comment #2) > I don't have any of these error messages, at least not with a pre-existing link. I see. My sqlcipher version was a bit old and the message about sqlcipher vanished after the package upgrade. Sorry. Feb 28 01:35:04 freebsd pkg[38698]: sqlcipher upgraded: 4.6.1_1 -> 4.13.0_1 > Maybe the errors are from a new link? I remember it took about two tries on a new link to populate all the group chats regardless of the sqlcipher interaction. They probably are, as stated by the developer: developer > I've also seen those errors on one device since yesterday. also, developer > This upstream PR [0] potentially fixes it. Flare should still run fine and receive messages without problems, at least that was the case for me, although I would not recommend using Flare in this state. I have tried using the updated libsignal-service-rs but failed to do so. I guess it's better to wait for a hotfix. Thank you! 0: https://github.com/whisperfish/libsignal-service-rs/pull/405
The latest version is v0.18.8 as of now and somehow I could not ditch the vendored/bundled openssl :(.
Created attachment 268509 [details] v1 It's trying to use bundled everything for bundled-sqlcipher, which is why particularly openssl-src is getting pulled in: https://github.com/Schmiddiii/presage/commit/642fb088bcb9c3c3ce6cd58d656e9705d07a465b I removed the openssl-{src,sys} crates from our side for good measure but it may not be necessary. Later runs of 0.18.4 were endlessly downloading stuff without any visible message updates. 0.18.8 seems to work properly.
Comment on attachment 268509 [details] v1 (In reply to Charlie Li from comment #5) Hi, Ah, I see. The patch looks good to me. Thank you!
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=b77bc6c9b4b34ac8ff92a2ae4b92b9d25692cfb4 commit b77bc6c9b4b34ac8ff92a2ae4b92b9d25692cfb4 Author: Charlie Li <vishwin@FreeBSD.org> AuthorDate: 2026-02-25 21:58:08 +0000 Commit: Charlie Li <vishwin@FreeBSD.org> CommitDate: 2026-03-04 15:17:29 +0000 net-im/flare: update to 0.18.8 Changelog: https://gitlab.com/schmiddi-on-mobile/flare/-/releases/0.18.8 While here, use databases/sqlcipher instead of bundled PR: 293450 Approved by: nxjoseph (maintainer) net-im/flare/Makefile | 10 +- net-im/flare/Makefile.crates | 291 +++++++++++---------- net-im/flare/distinfo | 588 +++++++++++++++++++++++-------------------- 3 files changed, 474 insertions(+), 415 deletions(-)