Open ianchanning opened 5 years ago
Hi, I have the same issue with the same version of SparkleShare (flatpak list -d
gives the same commit ID). I have used dazzle
to create the repository - once using dazzle create
and once using dazzle create-encrypted
. Both times, SparkleShare has asked for the password only on the first client I linked. Subsequent links succeed, but files are encrypted...
Edit: It is the same OpenSSL-version on all clients (1.1.0g) - in reference to issue #1855
Do you get a chance to access the files?
@MalteKiefer I think I just threw away the repository and switched to an un-encrypted repository
I've the same issue. I just spent an hour or two figuring out what was happening and in the end it seems I cannot decrypt the existing repo
You can find session logs by date and version information in:
What happened:
Synced encrypted repo created in v3.28, no password requested, the repo is synced but all files are encrypted.
This is similar to #1854 but in this case I have made sure that the encrypted repository was created with v3.28 as well.
What I expected to happen:
The application asks for a password and decrypts the repo locally.
This happens when:
log
flatpak list -d