stop leaking host fingerprint in client correlation id#1378
Conversation
…backs stop leaking a per-host fingerprint
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
jentfoo
left a comment
There was a problem hiding this comment.
LGTM, thank you for reconsidering this issue
Plain xid.New() derives its machine bytes from md5(hostname), which rides along on every OAST callback and lets the target (or third-party telemetry like GreyNoise) correlate scans back to the same operator. Keeps the timestamp prefix so format/sortability/server-side validation stay identical.
Closes #1349