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

Use graalvm native image without libsodium #847

Closed
3 tasks
brunovg opened this issue Sep 25, 2024 · 0 comments · Fixed by assimbly/base#97 or assimbly/custom-components#118
Closed
3 tasks

Use graalvm native image without libsodium #847

brunovg opened this issue Sep 25, 2024 · 0 comments · Fixed by assimbly/base#97 or assimbly/custom-components#118
Assignees
Milestone

Comments

@brunovg
Copy link
Collaborator

brunovg commented Sep 25, 2024

We used a custom graalvm base image with libsoudium, mainly because we had (on 4.15.x) the possibility of reverting to the old backend, where libsodium was already used to encrypt/decrypt tenant variables.

On 4.17.x it's not possible anymore.

What needs to be done:

  • use the initial backend (Assimbly) code, that uses a more recent type of encryption;
  • change ruby on rails code to use the same type of encryption;
  • migrate mongodb tenant variables that are encrypted, to use the same type of encryption.
@brunovg brunovg changed the title Remove libsodium from the base image Use graalvm native image without libsodium Sep 25, 2024
@brunovg brunovg self-assigned this Sep 25, 2024
@skin27 skin27 added this to the 5.0.0 milestone Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment