This adds support for profile keys. It's a first step for enabling avatars, profile names and groupsv2.
This has to be tested because it includes a rust library directly from Open whisper. The rust library is compiled to a shared library in c and then included with cgo.
I have included precompiled shared object to the module to not break the build chains in the first place.
But it would be better if the building is included in the ci.
For running anything with textsecure, the libzkgroup has to be placed in the LD_LIBRARY_PATH like
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PWD
The corresponding error message is
error while loading shared libraries: libzkgroup_linux_amd64.so: cannot open shared object file: No such file or directory
This adds support for profile keys. It's a first step for enabling avatars, profile names and groupsv2.
This has to be tested because it includes a rust library directly from Open whisper. The rust library is compiled to a shared library in c and then included with cgo. I have included precompiled shared object to the module to not break the build chains in the first place. But it would be better if the building is included in the ci.
For running anything with textsecure, the libzkgroup has to be placed in the
LD_LIBRARY_PATH
likeexport LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PWD
The corresponding error message iserror while loading shared libraries: libzkgroup_linux_amd64.so: cannot open shared object file: No such file or directory
Documentation can be improved a lot https://github.com/nanu-c/zkgroup
Should we add this to the Signal-golang organisation?