Deal properly with encrypted item updates accross connections
authorKevin Ottens <kevin.ottens@nextcloud.com>
Tue, 30 Jun 2020 15:20:02 +0000 (17:20 +0200)
committerKevin Ottens (Rebase PR Action) <er-vin@users.noreply.github.com>
Wed, 1 Jul 2020 16:58:29 +0000 (16:58 +0000)
commitd2e8cd4469162b203de6d9aaad2618014813dcbf
tree2c14515b22803b4449e9ff50019de8ede5a7bd4b
parent9a2d04720a5e644041cbbf1ef1badbc88b663bd8
Deal properly with encrypted item updates accross connections

In such cases we get a download for which _file is already the demangled
name and _encryptedFileName has the mangled information. This is
different to what we encountered so far where initially _file was
mangled and _encryptedFileName was empty. Let's deal with that case
properly.

Signed-off-by: Kevin Ottens <kevin.ottens@nextcloud.com>
src/libsync/propagatedownload.cpp
src/libsync/propagatedownloadencrypted.cpp