feat: encryption keys location can be specified by the storage implementation

[DeepDiver1975]

Description

This allows storage implementations to specify the location for encryption keys
https://github.com/owncloud/files_spaces needs this because the space does not belong to a user.

Related Issue

• Fixes https://github.com/owncloud/enterprise/issues/4687

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:
• Changelog item, see TEMPLATE

[cdamken]

Is there a process to move the keys that are already on the users to be moved in the spaces?

[DeepDiver1975]

Is there a process to move the keys that are already on the users to be moved in the spaces?

no - and I doubt that there is a general applicable solution.

keys are stored in the individual user's encryption key location.
I'd perform a manual analysis of the explicit system and move key files as needed ...

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

80.0% Coverage
0.0% Duplication

[DeepDiver1975]

Yeah - that's fishy ....

[JammingBen]

I'm afraid someone else has to come up with a more sophisticated solution, I don't see a general approach without mentioning the spaces app or providing a public interface to hook up to. This goes not only for this line here - we have multiple references to the spaces app, as you probably already have seen :(