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

Add .psec to the exclude sync extensions #12086

Open
2 tasks done
mmattel opened this issue Feb 28, 2025 · 0 comments · May be fixed by #12093
Open
2 tasks done

Add .psec to the exclude sync extensions #12086

mmattel opened this issue Feb 28, 2025 · 0 comments · May be fixed by #12093

Comments

@mmattel
Copy link
Contributor

mmattel commented Feb 28, 2025

Pre-submission Checks

  • I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
  • I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.

Feature description

Add a new extension to the default exclude sync list.

Proposed solution

Add the .psec extension to the default extension exclude list.
This will prevent files with such an extension from being synced.

Alternative solutions you considered

Adapt Infinite Scale that files with such an extension will not be processable by the API.

Additional context

Files with the psec extension are necessary for password protected folders.

  1. See the description in the PPF's readme for details how PPF works and for impacts and possible solutions inside the webUI.

  2. Because of the way it got implemented, there are some things that can be potential usability issues with likely major bad user experiences.

    1. First there is the deletion issue (PPF Location) which can be mitigated by following the suggested solution.
    2. Second there is the moving/renaming issue which also can be mitigated following the PPF Location suggestion.

    But those mitigations only work as long the users stays in the webUI. Atm where sync apps are involved, these mitigations can and - I strongly believe - will be an issue that are a major cause for bad user experience. The referenced readme tells the story and you only need to imagine some PPF usecases plus creative users playing around, read it carefully!

There are two possible solutions, which can also be done in parallel:

  • A short term fix that should consistently be added into all sync apps by disallowing any sync of files having the psec extension. This would reduce the issue to the webUI in a very short timeframe.
  • A longterm and consistent fix in the ocis backend that prevents psync files passing the API except the webUI.

Notes:

  • ocis 7.1 will be released in the first week of March (next week), any change will not make it in.
  • The next ocis release that will be set productive is min +6m to go
  • The next Desktop/Android app release is in March
  • An update for iOS can be made quickly

@DeepDiver1975 as dicussed
@kobergj @LukasHirt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant