I'm using the pre-release 2.4.0-beta2. In the settings for KeeShare, there is no panel for the "Own certificate", as it is mentioned and shown in the documentation of the feature branch: https://github.com/hicknhack-software/keepassxc/blob/feature/sharing_groups/docs/QUICKSTART.md#enable-sharing
This is how the settings look for me:
I'm not sure, whether this was dropped somewhere in the development. However, when I want to synchronize a group, I get the follwing warning: "We cannot verify the source of the shared container because it is not signed. [...]". So I expect there is the pssibility to sign the container.
KeePassXC - Version 2.4.0-beta2
Build Typ: PreRelease
Revision: 9bc20f0
Bibliotheken:
Betriebssystem: Windows 10 (10.0)
CPU-Architektur: x86_64
Kernel: winnt 10.0.17763
Aktivierte Erweiterungen:
I forgot to build in the protected share for beta 2. It'll be in the final
Own certificate panel is still missing for me in Arch and AppImage version. Also when selecting an certified keeshare-file (kdbx.share) I get an error stating it isn't supported.
KeeShare secure is not supported in AppImage at this time. You can use the snap build or build from source.
I have the same issue under OSX using the official 2.4.0 release: the panel to generate a certificate is missing. Should I open another issue for that?
No, that's because homebrew does not provide quazip5. I guess we may have to submit that ourselves.
In arch I also don't have certificate panel. Is this Arch problem or I do just have to install some library?
You need to compile with -DWITH_XC_KEESHARE_SECURE=ON. It's not included in -DWITH_XC_ALL as of yet.