Skip to content

fix(toolbox-core): Add strict flag support to sync client #230

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

Merged
merged 6 commits into from
May 16, 2025

Conversation

anubhav756
Copy link
Contributor

No description provided.

@anubhav756 anubhav756 self-assigned this May 8, 2025
@anubhav756 anubhav756 requested a review from a team as a code owner May 8, 2025 10:47
@anubhav756 anubhav756 changed the title fix(toolbox-core): Add strict flag validation to sync client fix(toolbox-core): Add strict flag support to sync client May 8, 2025
@anubhav756 anubhav756 force-pushed the anubhav-sync-client-test branch from 916c865 to e08caae Compare May 12, 2025 14:13
@anubhav756 anubhav756 force-pushed the anubhav-sync-strict branch from 8c38950 to bb15dbf Compare May 12, 2025 14:13
@anubhav756 anubhav756 force-pushed the anubhav-sync-client-test branch from e08caae to 91c2731 Compare May 13, 2025 11:26
@anubhav756 anubhav756 force-pushed the anubhav-sync-strict branch from bb15dbf to d6f6d1e Compare May 13, 2025 11:27
@anubhav756 anubhav756 force-pushed the anubhav-sync-client-test branch from 91c2731 to 13079a1 Compare May 14, 2025 12:40
@anubhav756 anubhav756 force-pushed the anubhav-sync-strict branch from d6f6d1e to 6027fae Compare May 14, 2025 12:42
@anubhav756 anubhav756 force-pushed the anubhav-sync-client-test branch 2 times, most recently from 81856a3 to b70dfa7 Compare May 15, 2025 08:47
@anubhav756 anubhav756 force-pushed the anubhav-sync-strict branch from b00577c to 8286079 Compare May 15, 2025 08:49
Base automatically changed from anubhav-sync-client-test to main May 16, 2025 11:06
@anubhav756 anubhav756 changed the base branch from main to anubhav-sync-client-test May 16, 2025 11:13
Base automatically changed from anubhav-sync-client-test to main May 16, 2025 14:12
This change introduces a warning that is displayed immediately before a tool invocation if:
1. The invocation includes an authentication header.
2. The connection is being made over non-secure HTTP.

> [!IMPORTANT]
The purpose of this warning is to alert the user to the security risk of sending credentials over an unencrypted channel and to encourage the use of HTTPS.
@anubhav756 anubhav756 force-pushed the anubhav-sync-strict branch from 8286079 to 19a8330 Compare May 16, 2025 15:49
@anubhav756 anubhav756 merged commit 4e19a3c into main May 16, 2025
19 checks passed
@anubhav756 anubhav756 deleted the anubhav-sync-strict branch May 16, 2025 16:53
@release-please release-please bot mentioned this pull request May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants