Upload encryption with WASM

[sampsapenna]

Description

Upload encryption using the existing upload runner ecosystem with resumable.js. Encryption is done using libcrypt4gh written in C and compiled with WebAssembly as a target. Dockerfile-build-crypt and Dockerfile-build-crypt-devel handle building the encryption into the UI as of now.

Related issues

• Implements MVP functionality support encryption for uploaded objects #262
• Implements issue Support encryption for objects – continued with proper UI integration #380

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update (this needs a follow up PR)

Changes Made

• Rudimentary UI integration for encryption
• Encryption using libcrypt4gh in C
• build files for encryption library

Testing

• Unit Tests
• Integration Tests
• Tests do not apply
• Needs testing (start an issue or do a follow up PR about it)

Mentions

[blankdots]

seems this is a problem as well :(

[sampsapenna]

Latest push includes multiple changes:

1. Fix issues with upload redirection through HAProxy
2. Add support for folder uploads when uploading encrypted files
3. Unify encrypted and ordinary upload UIs
4. Implement automatic configurable default key fetch
5. Add new, better upload UI allowing for editing files, keys and container name (no longer forcing default container names)
6. Improve drag-n-drop file input, and add support for encrypted uploads using drag-n-drop
7. Add encryption process error handling and informational messages
8. Check for upload size to notify user on too large uploads

[blankdots]

image versions (alpine) need updating and we need to have our own libcrypt4gh repo at CSCfi org.
small improvements in the docs need to be managed.

Note: I think we need to add follow-up issue for testing the C code as well as cypress tests to test the encryption interaction in front-end

Suggestion (not a change request): Instead of building the wasm as part of the image we can build it as part of the CI and add a conditional in the final image if that binary exists we enable that feature if not we don't. This will have the benefit of having fewer images to handle and keep track of.

Will come back with more suggestions after I test as well

[blankdots]

there could be some other UI improvements, however let us tackle them as part of another issue.

[sampsapenna]

Generates issues #462 #463