Cherry-pick #22151 to 7.10: Fix zeek connection pipeline#22160
Merged
leehinman merged 2 commits intoelastic:7.10from Oct 27, 2020
Merged
Cherry-pick #22151 to 7.10: Fix zeek connection pipeline#22160leehinman merged 2 commits intoelastic:7.10from
leehinman merged 2 commits intoelastic:7.10from
Conversation
Contributor
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
- connection state for rejected is 'REJ' Closes elastic#22149 (cherry picked from commit 5469c46)
a1b6691 to
73bc723
Compare
Contributor
andrewkroh
approved these changes
Oct 27, 2020
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.
Cherry-pick of PR #22151 to 7.10 branch. Original message:
What does this PR do?
https://docs.zeek.org/en/current/scripts/base/protocols/conn/main.zeek.html
Why is it important?
Rejected connection states weren't matching.
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
Related issues