Skip to content
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

test: add test for ldap.request.operation - v1 #2206

Conversation

AkakiAlice
Copy link
Contributor

@AkakiAlice AkakiAlice commented Dec 23, 2024

Ticket: 7453

Description:

  • Add S-V test for ldap.request.operation keyword

Redmine ticket: https://redmine.openinfosecfoundation.org/issues/7453
Suricata PR: OISF/suricata#12321


## PCAP

This PCAP was generated with flowsynth v1.4.1.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if you can simply reuse some (not all) ldap tests and add a rules file with them

@@ -0,0 +1,9 @@
alert tcp any any -> any any (msg:"Test LDAP bind request"; ldap.request.operation:0; sid:1;)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is good for a first iteration.

In a next iteration, we want to have both signatures ldap.request.operation:0; and ldap.request.operation:bind; (I say bind but we should take whatever is being logged as metadata)

See websocket.opcode and usage of git grep EnumString in suricata

@catenacyber
Copy link
Collaborator

Replaced by #2216 right ?

@catenacyber catenacyber closed this Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants