Skip to content

Adding knowledge about not using ports below 1024 on unix-based OS #126248

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tsimiz
Copy link

@tsimiz tsimiz commented Mar 18, 2025

There is at least one open issue at az-cli GitHub about getting errors with 'az network bastion tunnel' command when using local port 22 to open the tunnel on unix-based operating system. As ports below 1024 are privileged ports only accessible by root I would recommend that the information about this is added into examples.

There is at least one open issue at az-cli GitHub about getting errors with 'az network bastion tunnel' command when using local port 22 to open the tunnel on unix-based operating system. As ports below 1024 are privileged ports only accessible by root I would recommend that the information about this is added into examples.
Copy link
Contributor

@tsimiz : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 2d3b93f:

✅ Validation status: passed

File Status Preview URL Details
includes/bastion-native-connect-tunnel.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@ttorble
Copy link
Contributor

ttorble commented Mar 19, 2025

@cherylmc

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Mar 19, 2025
@v-dirichards
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@cherylmc
Copy link
Contributor

Product team is investigating.

@v-ccolin
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

@cherylmc
Copy link
Contributor

#assign:isamorris99

@v-dirichards
Copy link
Contributor

@isamorris99 Could you review this proposed update to the article and enter #sign-off in a comment if it's ready to merge?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants