Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable16] Better check reshare permissions #16127

Merged
merged 4 commits into from
Jun 27, 2019
Merged

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #16097

nickvergessen and others added 4 commits June 27, 2019 14:30
Before this change the node you shared was checked for permissions.
This works when you reshare the folder that was shared with you.
However when you reshared a subfolder (e.g. as public link),
you could afterwards update the permissions and grant
create+update permissions although the share you receive was read-only.

Signed-off-by: Joas Schilling <coding@schilljs.com>
The admin user is not deleted after each integration test is run, so
folders created by the admin user in one test are still there when the
next tests run; tests should be independent one from each other, so a
regular user that is created and deleted for each test should be used
instead.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
The tests check an user share and a link share; there is a slight
difference in style between them as each one is based on the test above
it, which tests increasing reshare permissions.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
@nickvergessen nickvergessen added the 4. to release Ready to be released and/or waiting for tests to finish label Jun 27, 2019
@rullzer rullzer merged commit 0f8a3e8 into stable16 Jun 27, 2019
@delete-merged-branch delete-merged-branch bot deleted the backport/16097/stable16 branch June 27, 2019 20:10
@rullzer rullzer mentioned this pull request Jun 28, 2019
5 tasks
@rullzer rullzer mentioned this pull request Sep 12, 2019
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants