Encrypt the game name and player name fields for copi.owasp.org

[sydseter]

We should make sure the game name and player name fields for copi.owasp.org is encrypted. During migration, the data not encrypted should get encrypted by the application. The key need to be stored as an environment variable when deployed.

[Klath123]

Hi @sydseter , I would like to work on this issue.

I can implement encryption and decryption for the game name and player name fields, ensure existing unencrypted data is securely migrated, and manage the encryption key through environment variables as suggested. I will also make sure the changes integrate cleanly with the existing application workflow.
Please let me know if I can proceed and if there are any preferred encryption approaches or libraries for this project.

[sydseter]

I have assigned you.

[InFiNiTy0639]

@sydseter can i work on this?

[sydseter]

@InFiNiTy0639 Have a look at the issues that not is assigned to anyone.

[Arunodoy18]

Hi 👋

I’d like to take this on.

Proposed approach:

• Implement field-level encryption for game.name and player.name using application-level encryption (not database-level).
• Store the encryption key securely via environment variable (e.g. COPI_ENCRYPTION_KEY).
• Introduce a migration strategy:
  • Keep existing plaintext data readable.
  • Encrypt legacy records during application boot or via a one-time migration task.
• Ensure decryption happens transparently at the schema level so existing queries continue to work.

I will make sure:

• No breaking changes to existing flows.
• Encryption key is never hardcoded.
• Backward compatibility is preserved during transition.

Please let me know if there are any preferred encryption libraries or patterns already used in the project before I proceed.