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

Unshare from user must lock path to avoid recipient access #17244

Closed
PVince81 opened this issue Jun 29, 2015 · 7 comments
Closed

Unshare from user must lock path to avoid recipient access #17244

PVince81 opened this issue Jun 29, 2015 · 7 comments

Comments

@PVince81
Copy link
Contributor

PVince81 commented Jun 29, 2015

Steps to reproduce

  1. Enable transactional file locking
  2. Create two users "user1" and "user2"
  3. Login as "user1"
  4. Create a folder "test"
  5. Share "test" with "user2"
  6. Add sleep(30); here to delay the unshare operation:
    $toDelete = array();
  7. Unshare "test" from "user2"
  8. At the same time, try downloading or modifying the contents of the folder "test" as user2 (recipient)

Expected result

Folder "test" is exclusively locked.

Actual result

Folder can still be tempered with while the unshare operation is running.

Version

ownCloud 8.1 git master b88a0e7

Note: this should also prevent two unshare operations to run in parallel.

@PVince81
Copy link
Contributor Author

@jnfrmarks @icewind1991 @schiesbn

@PVince81
Copy link
Contributor Author

@DeepDiver1975 @cmonteroluque I scheduled to 8.2, I don't think there is time left for this

@PVince81 PVince81 changed the title Unshare from user must lock recipient path Unshare from user must lock path to avoid recipient access Jun 29, 2015
@PVince81
Copy link
Contributor Author

Not sure if sev high or medium as I don't know what kind of breakage could happen.
@schiesbn do you see anything bad happening (ex: data loss) when updating sharing keys during an unshare while people access the files ?

@ghost
Copy link

ghost commented Oct 1, 2015

This issue will fall off 8.2 if not resolved by 6 Oct

@ghost ghost modified the milestones: backlog, 8.2-current Oct 5, 2015
@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

@ownclouders
Copy link
Contributor

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.)

@stale
Copy link

stale bot commented Sep 21, 2021

This issue has been automatically closed.

@stale stale bot closed this as completed Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants