-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[v16] Restrict cipher suites for Desktop Access in FIPS mode #43158
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Updates to the new boring fork's hash with FIPS enforcement. This hash is on a branch and should be changed once that branch is merged. It includes the `set_fips_compliance_policy` function which is used to enforce FIPS-valid ciphers in the connection. This commit also updates `Cargo.lock` generally by having called `cargo update` before committing the changes. * reverts previous changes such that we are again using clang 12.0.0 rather than 14.0.6 * Updates to latest boring hash * removes rdp client for fips builds on arm64 * updates e to isaiah/enforce-fips head * Updates boring ref * Updates boring ref * Update Makefile Co-authored-by: Zac Bergquist <[email protected]> * Adds note about desktop access fips to fedramp docs * Updates boring hash to now-merged HEAD of the `teleport` branch * update e to latest head * try adding --nocheck to see if that fixes arm64 builds * udates to latest HEAD * latest e * Update docs/pages/access-controls/compliance-frameworks/fedramp.mdx Co-authored-by: Zac Bergquist <[email protected]> * Update docs/pages/access-controls/compliance-frameworks/fedramp.mdx Co-authored-by: Zac Bergquist <[email protected]> * Update docs/pages/access-controls/compliance-frameworks/fedramp.mdx Co-authored-by: Zac Bergquist <[email protected]> * noteable --> notable --------- Co-authored-by: Zac Bergquist <[email protected]>
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
🤖 Vercel preview here: https://docs-c5cvof6xl-goteleport.vercel.app/docs/ver/preview |
zmb3
approved these changes
Jun 18, 2024
probakowski
approved these changes
Jun 19, 2024
ibeckermayer
added
the
no-changelog
Indicates that a PR does not require a changelog entry
label
Jun 19, 2024
🤖 Vercel preview here: https://docs-6hphk4d1l-goteleport.vercel.app/docs/ver/preview |
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Jun 19, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Jun 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport
desktop-access
documentation
no-changelog
Indicates that a PR does not require a changelog entry
rdp
size/sm
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
backport #42277 to branch/v16