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

docs: deprecate rsadecrypt #18856

Merged
merged 2 commits into from
Oct 24, 2023
Merged

docs: deprecate rsadecrypt #18856

merged 2 commits into from
Oct 24, 2023

Conversation

schmichael
Copy link
Member

@schmichael schmichael commented Oct 24, 2023

rsadecrypt uses PKCS #1 v1.5 padding which has multiple known weaknesses. While it is possible to use safely in Nomad, we should not encourage our users to use bad cryptographic primitives.

If users want to decrypt secrets in jobspecs we should choose a cryptographic primitive designed for that purpose. rsadecrypt was inherited from Terraform which only implemented it to support decrypting Window's passwords on AWS EC2 instances:

hashicorp/terraform#16647

This is not something that should ever be done in a jobspec, therefore there's no reason for Nomad to support this HCL2 function.

Preview to save you a few clicks:
image

`rsadecrypt` uses PKCS #1 v1.5 padding which has multiple known
weaknesses. While it is possible to use safely in Nomad, we should not
encourage our users to use bad cryptographic primitives.

If users want to decrypt secrets in jobspecs we should choose a
cryptographic primitive designed for that purpose. `rsadecrypt` was
inherited from Terraform which only implemented it to support decrypting
Window's passwords on AWS EC2 instances:

hashicorp/terraform#16647

This is not something that should ever be done in a jobspec, therefore
there's no reason for Nomad to support this HCL2 function.
Copy link
Member

@tgross tgross left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Copy link
Contributor

@angrycub angrycub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aww yiss!

@schmichael schmichael added backport/website This will backport PR changes to `stable-website` && the latest release-branch backport/1.6.x backport to 1.6.x release line labels Oct 24, 2023
@schmichael schmichael merged commit 9b3c38b into main Oct 24, 2023
@schmichael schmichael deleted the docs-rsadeprecate branch October 24, 2023 22:48
@angrycub
Copy link
Contributor

@schmichael Did you keep the whitespace standoff after the opening tag. If not, the markdown doesn't render. If so, it should render the markdown inside

Copy link

github-actions bot commented Feb 7, 2025

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 7, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport/website This will backport PR changes to `stable-website` && the latest release-branch backport/1.6.x backport to 1.6.x release line
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants