[Bug]: Deleting "remote wipe" of device too soon results in device never being wiped
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
nextCloud Server version: 29.0.8
After marking a device for remote wipe (in the security section of the personal account settings), and then clicking the trashbin (delete) icon beside that device, before it has completed wiping, the wiping never happens. It also puts that client into a broken state, and can access all the data that was already sync'd to that device.
Steps to reproduce
- Target device is off (Ubuntu Linux on a laptop, in this case), but already sync'd data with the desktop client to the computer before being turned off
- Go into webGUI for test account, into the Security section
- Select target device, mark for "remote wipe", enter password and proceed
- Click on the trashbin that now shows up beside the device marked for "remote wipe" in the same window before the device has had a chance to turn on
Expected behavior
- Outline that deleting before the remote wipe is complete means the remote wipe doesn't happen (in the UX)
- Make it so that the remote wipe happens even if it is deleted before it executes
- Make it so I still get a notification of the remote wipe (which I did not in this case) just like if you had not clicked the trashbin
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Security section's remote-wipe flow and reproduce the sequence of marking a device for remote wipe, then deleting it before the device reconnects. Trace what happens to the pending wipe and notification after deletion; done means the wipe still executes, the user is notified, and the UX explains the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100