Conversation
…a Revisiting TDS draft tds-zeek.ipynb runs Zeek 8.2 with zeek-tds v0.2.0 in Docker over the 2009 capture, reads the logs with ParseZeekLogs and redoes the Part 4 analysis, showing the two structural cases tshark could not resolve: a call spanning two packets and a message holding two calls. The 2018 pyshark notebook stays. CI builds the image before executing notebooks. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Fetches the small public captures from the zeek-tds v0.2.0 tag and walks tds_login, tds_error, ssl and ntlm under the same uid, MARS sessions in tds.log, the opt-in tds_result.log, ssrp.log and the notices. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
Adds tds-zeek.ipynb alongside the 2018 pyshark notebook: Zeek 8.2 with zeek-tds v0.2.0 runs in Docker over the same capture, ParseZeekLogs loads the logs, and the Part 4 analysis is redone with every procedure call, its parameters and prepared-statement SQL. It logs 17 calls where the pyshark pass identified 15, and shows why: one call spans two TDS packets (no reassembly in tshark) and one message holds two calls (tshark reports the first). Includes the Dockerfile, a README row and a draft post docs/2026-09-revisiting-tds.md for review. CI builds the image before executing notebooks.
🤖 Generated with Claude Code