Uh oh!
There was an error while loading. Please reload this page.
Prevent creating users with existing files - #18130
Conversation
rullzer
commented
Nov 27, 2019
tests do boom |
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
7f919be to
6004f62Comparenickvergessen
commented
Dec 4, 2019
I fixed our "unit" tests.... arg |
thomas-mc-work
commented
Mar 26, 2020
This change prevented us from a migration of files: We have provided only the files from an old Nextcloud instance into the data directory of a new one. With Nextcloud 17 this scenario was fine. The user could log in and see his files. Now they get an error 403 without any further info. I couldn't even find something about that in the log file.
|
nickvergessen
commented
Mar 26, 2020
The link was missing, it is #16196 |
Thank you for your quick reply @nickvergessen! Actually my on only problem is about line 642: This was only |
nickvergessen
commented
Mar 26, 2020
Well before it was hardcoded to what we know. But if an app creates something in root, it could still be overwritten by creating a user. I don't know how you create your users, but what you can do is:
|
Yes, that's possible. But we've got about 700 Users. And they are provided by an external auth module (user_cas), so Nextcloud isn't aware of them before they log in the first time. Maybe it would have been good to clean the data dir by moving the user accounts into a separate sub folder named
Has this really been an issue to someone? Are apps even encouraged to write into this folder? |
nickvergessen
commented
Mar 26, 2020
Well it's a security thread so we fix it.
Not encouraged, but we also don't prevent it We will not revert this, in case you accept this security risk you can change your code. But don't come back here when your nextcloud got hacked because of it 😉 |
Signed-off-by: Joas Schilling coding@schilljs.com