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

Don’t downgrade SSH port forwarding in roles for clients 17.1.0 and above #50645

Merged
merged 2 commits into from
Jan 8, 2025

Conversation

bl-nero
Copy link
Contributor

@bl-nero bl-nero commented Dec 31, 2024

Previously, v18.0+ clients got the port forwarding options downgraded.

@bl-nero bl-nero force-pushed the bl-nero/fix-port-forwarding-downgrade-version branch from 263ad72 to 319a1e2 Compare December 31, 2024 16:48
@bl-nero bl-nero added the no-changelog Indicates that a PR does not require a changelog entry label Dec 31, 2024
Copy link
Contributor

@fheinecke fheinecke left a comment

Choose a reason for hiding this comment

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

LGTM but I don't really work on product changes, and I don't have a good understanding of the implication of these changes. Not sure why GH assigned me. Approving to unblock.

}
if supported, err := utils.MinVerWithoutPreRelease(
clientVersion.String(),
minSupportedSSHPortForwardingVersion.String()); supported || err != nil {
Copy link
Contributor

Choose a reason for hiding this comment

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

The current PR description states:

Don’t downgrade SSH port forwarding in roles for v18.0+

However, the minSupportedSSHPortForwardingVersion is actually set to Major: 17, Minor: 1, meaning the change ensures SSH port forwarding is not downgraded starting from version 17.1.0 and upwards, not just for v18.0+.

To make the description clearer and more accurate, could you update it to:

Don’t downgrade SSH port forwarding in roles for clients 17.1.0 and above

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point, thanks :)

Copy link
Contributor

@smallinsky smallinsky left a comment

Choose a reason for hiding this comment

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

@bl-nero bl-nero changed the title Don't downgrade SSH port forwarding in roles for v18.0+ Don’t downgrade SSH port forwarding in roles for clients 17.1.0 and above Jan 8, 2025
@bl-nero
Copy link
Contributor Author

bl-nero commented Jan 8, 2025

LGTM but I don't really work on product changes, and I don't have a good understanding of the implication of these changes.

That's why I requested @eriktate to review, as he wrote this part. Also, assuming that the original idea used to be allowing granular options in many major versions, starting from different minor number in each, I asked around whether there are plans to support granular options in v16, and Zac said no. That's why I decided that "version >= 17.1" is a good final choice.

@bl-nero bl-nero enabled auto-merge January 8, 2025 12:46
@bl-nero bl-nero added this pull request to the merge queue Jan 8, 2025
Merged via the queue into master with commit 26a0ac8 Jan 8, 2025
41 checks passed
@bl-nero bl-nero deleted the bl-nero/fix-port-forwarding-downgrade-version branch January 8, 2025 13:52
@public-teleport-github-review-bot

@bl-nero See the table below for backport results.

Branch Result
branch/v17 Create PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/branch/v17 no-changelog Indicates that a PR does not require a changelog entry size/sm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants