-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Make Imaginary work with server-side encryption #34262
Comments
Hi, would you prefer to decrypt the files (to sent them unencrypted to the imaginary service) or fallback to local preview generation? |
Ideally i'd like to send them unencrypted to the imaginary service, as i need it ( i unencrypted my whole server for now ). I think it would also "solve" https://github.com/nextcloud/previewgenerator 's known issue if the \OC\Preview module does the unencryption before sending the data to the plugin behind |
I think this is a feature request to make imaginary work with sse |
Any plans to fix this? Would be really nice to be able to use Imaginary AND keeping the stored data secure. |
Bug description
When using server-side encryption, if you enable the usage of Imaginary micro service, all picture are sent encrypted to imaginary, making the micro service totally useless ( and silently, you can only check that by seeing errors 400 in imaginary log, instead of normal 200 answers)
Steps to reproduce
Expected behavior
Previews are correctly generated ( by not using Imaginary with server side encryption, or by having the server unencrypt files before sending them to imaginary)
Installation method
Community Manual installation with Archive
Operating system
RHEL/CentOS
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
No response
Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: