Tim van der Molen
Tim van der Molen
I don't think this is a problem in sigbak. Are you able to compile other code using the same compiler and compiler flags? For example, try this program: ``` #include...
I have no idea, sorry. Perhaps you could ask the MSYS2 people? Or just build sigbak in Cygwin or WSL.
sigbak is a Unix program and expects POSIX APIs like `openat()` to be available. I don't know MSYS2 well, but doesn't it have a POSIX emulation mode? Otherwise you'd have...
> MSYS2 indeed has the Cygwin POSIX emulation layer, but there is no package for protobuf-c Can you build protobuf-c as part of your sigbak build? I'm doing something similar...
I'm going to close this issue, too. Feel free to reopen.
It looks like you have to update sigbak. Run the following the commands in the Cygwin terminal: ``` git -C sigbak pull PKG_CONFIG_PATH=/usr/local/lib/pkgconfig make -C sigbak clean install ``` Then...
I'm going to close this. If you still need help, feel free to let me know.
As @flatz explained, Signal Desktop recently started to encrypt the database key in `config.json`. The old unencrypted key would continue to be available as a temporary fallback, but this fallback...
It's not less secure. Before the Signal update, you had an unencrypted key in `config.json`. Now you have an unencrypted key in `passfile`. Nevertheless, it's a good idea either to...
sigtop can now also read the password from standard input so you won't have to create a `passfile`. For example: ``` security find-generic-password -ws "Signal Safe Storage" | sigtop db...