Skip to content

Add AllowInsecureConnections to push command #3456

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Aug 15, 2025
Merged

Add AllowInsecureConnections to push command #3456

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8d51573
Add AllowInsecureConnections to push command
Nigusu-Allehu Aug 6, 2025
b8bc6bf
link
Nigusu-Allehu Aug 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/reference/cli-reference/cli-ref-push.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,9 @@ where `<packagePath>` identifies the package to push to the server.

## Options

- **`-AllowInsecureConnections`**
Copy link

Copilot AI Aug 6, 2025

Choose a reason for hiding this comment

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

The option name should be consistent with typical CLI parameter formatting. Consider using --allow-insecure-connections (kebab-case with double dashes) or -AllowInsecureConnections if following PowerShell-style conventions, but verify this matches the actual implementation.

Copilot uses AI. Check for mistakes.
Allows pushing to HTTP sources (insecure). For more information, refer to https://aka.ms/nuget-https-everywhere.

Copy link

Copilot AI Aug 6, 2025

Choose a reason for hiding this comment

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

The documentation should include a security warning about the risks of using insecure connections, such as potential exposure of API keys and package contents to network interception.

Suggested change
> [!Warning]
> Using insecure (HTTP) connections can expose your API keys and package contents to interception by malicious actors. Avoid using this option unless absolutely necessary and only in trusted environments. Always prefer secure (HTTPS) connections to protect sensitive information.

Copilot uses AI. Check for mistakes.
- **`-ApiKey`**

The API key for the target repository. If not present, the one specified in the config file is used.
Expand Down