Ad-hoc tool to test TLS endpoints using node_key from nodes#875
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Add a small stdlib-only debugging script for exercising
osctrl-tlsendpoints with raw HTTP and dumping full request/response details.What Changed
tools/debug_tls_endpoints.pytools/test_debug_tls_endpoints.pyBehavior
enroll,config,log,read,write, andallosquery.flagsosquery.secretfor enroll when needednode_key+identifierfor testing existing node flows without enrolling a new nodeWhy
Debugging TLS/osquery behavior was awkward and usually required either a real node enrollment or hand-building curl payloads. This gives us one small tool for replaying the same endpoint shapes the backend expects.
Validation