Hi all !
NC server 13.0.3 running on Ubuntu 16.04 LTS + MySQL
Client E2E tech preview running on Windows 7 64bits
Android 3.0.2 client running on Android 8.0 on a Samsung Galaxy S8+
When I add files in the local (PC) folder which is to be E2E encrypted on the server, I get really weird behavior when I force-sync my Android phone :

tl;dr : I'm happy to test and preview the E2EE feature, yet hopefully I just add, change & remove only test files otherwise I woud have lost data.
I'm not sure howI can help.
G_LL_M
We will provide a new tech preview soonish. We have a much newer version of the e2ee (#251) merged into master. I believe this problem has been fixed but just in case cc @tcanabrava @dantti.
I believe it's been fixed as the desktop client store files with UUIDs as names now, of course this might be created by the Android app which I dunno if it's using UUIDs already, but the behavior that deleted and downloaded the file again should be fixed now.
Great !
Can't wait to test the next tech preview version :)
Will update the issue when done !
Thanks all !
Should be fixed.
Edit : woooops, I did not see the 2.5 Release flag you added 3 days ago :-)
Has "soonish" been postponed or rescheduled ? ;-)
:)
but soonish became today: https://download.nextcloud.com/desktop/daily/Windows/.
hey !
I just installed the 28.06 daily.
I had to enter the 12 words for the decryption.
It seemed to have failed to decrpt it locally, but I do not knowwhy because when I look at the mnemonic, they seem fine.
Here is the error messages i get :

Also, I cannot remove any file fomr my E2EE test folder (eiehter from Android or from Windows). I'm kinda stuck with the actual files + all the crappy files the E2E generated (see the issue title)
Do I need to wait for a NC server update so that the E2E works again ?
Thanks
GLLM
NC : 13.0.4 on ubuntu 16.04 LTS - MySQL
Windows client : Nextcloud-2.5.0.0-Debug-20180628
Android client : 3.2 stable
It has been a while. I think this is fixed now as in "we probably can't reach that state anymore". For the stale files you pointed out I'm not sure we can do anything about them anymore I suspect they ended up in a broken state during the early tech preview.
I will close this one for now, but please if you manage to corrupt files again like you initially reported with upcoming 2.7 releases feel free to open an issue with an updated reproduction procedure.
HI @er-vin
no pb.
Long ago, I actually yet sadly resorted to stop using/hoping for the E2E encryption of files in Nextcloud ... especially since this feature (or feature-to be, maybe one day), is not advertised at all by Nextcloud.
Thanks
especially since this feature (or feature-to be, maybe one day), is not advertised at all by Nextcloud.
Well, erm…
@KopfKrieg : well it's 2y ago & NC 13 ... and I have never heard anything about E2E encryption in NC ever since.
When this was released, I installed it, tried it. Had many bugs, file which could not be decipher. Other which could not be visible.
I removed it 1.5y later because it was not mature and full-featured enough. So I've been waiting for something more stable and usable.
I think I can probably find the github issue which explained that quite some things needed to be changed...
Anyway, the mere fact that Nextcloud does not communicate about it anymore (2 years) despite a context which could be quite favorable to it, is for me the sign that the priority is not on this. At least for the moment.
I may try it once again to check but I have low expectations ;)
have a good day