Open nicktrn opened 1 year ago
/attempt #10805
Sorry, there's nothing to attempt here, the labeling bot is just having fun.
Maige update instructions to avoid bounties
Here are your new instructions:
"Update instructions to avoid bounties"
Feel free to provide feedback.
Maige update instructions to avoid "š Bounty"
Here are your new instructions:
"Update instructions to avoid bounties and š Bounty"
Feel free to provide feedback.
Not stale.
Issue Summary
https://github.com/calcom/cal.com/blob/7c237736365c188e1762691fa4376a5e71daeee5/.env.example#L88-L91
Currently, 24 random bytes are expanded via base64-encoding to match the required AES-256 key length of 32 bytes.
This is effectively AES-192 security (with two additional rounds).
Recommendations
The key encoding could also be chosen dynamically based on its length and an additional env var
OLD_ENCRYPTION_KEY
provided to migrate old secrets on-demand.As part of the migration, I would recommend switching over to
aes-256-gcm
. Using non-authenticated AES in CBC mode is not recommended when GCM is available.Could also take care of this at the same time:
6028
From SyncLinear.com | CAL-2901