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

Add keyword to match on 'raw' TLS certificates #3542

Closed
wants to merge 3 commits into from

Conversation

thus
Copy link
Contributor

@thus thus commented Nov 14, 2018

Add new keyword tls_cert to match on the 'raw' TLS certificate. This keyword matches on the first certificate in the certificate chain.

Example:
alert tls any any -> any any (msg:"test tls_cert"; tls_cert; content:"|01||02||03||04|"; sid:1;)

https://redmine.openinfosecfoundation.org/issues/2670

Prscript:

Add keyword to do "raw" matching on the TLS certificate buffer.

Example:
  alert tls any any -> any any (msg:"tls_cert test"; tls_cert; \
          content:"|01||02||03||04|"; sid:1;)
Rename buffer type for the old TLS keywords to avoid a name conflict
with the 'tls_cert' keyword.
@thus thus requested review from norg and a team as code owners November 14, 2018 15:23
@thus thus closed this Nov 15, 2018
@thus
Copy link
Contributor Author

thus commented Nov 15, 2018

Replaced by #3545

victorjulien added a commit to victorjulien/suricata that referenced this pull request May 2, 2022
Set correct direction for PORT mode, where the server connects
to the client.

The direction is not also strictly enforced. No data in the wrong
direction will be accepted to setup the file or to be added to the
file after setup.

This also fixes files getting closed twice.

Adds some general cleanups.

Bug: OISF#3542.
victorjulien added a commit to victorjulien/suricata that referenced this pull request May 3, 2022
Set correct direction for PORT mode, where the server connects
to the client.

The direction is not also strictly enforced. No data in the wrong
direction will be accepted to setup the file or to be added to the
file after setup.

This also fixes files getting closed twice.

Adds some general cleanups.

Bug: OISF#3542.
(cherry picked from commit 07bf921)
victorjulien added a commit to victorjulien/suricata that referenced this pull request May 3, 2022
Set correct direction for PORT mode, where the server connects
to the client.

The direction is not also strictly enforced. No data in the wrong
direction will be accepted to setup the file or to be added to the
file after setup.

This also fixes files getting closed twice.

Adds some general cleanups.

Bug: OISF#3542.
(cherry picked from commit 07bf921)
victorjulien added a commit to victorjulien/suricata that referenced this pull request May 4, 2022
Set correct direction for PORT mode, where the server connects
to the client.

The direction is not also strictly enforced. No data in the wrong
direction will be accepted to setup the file or to be added to the
file after setup.

This also fixes files getting closed twice.

Adds some general cleanups.

Bug: OISF#3542.
(cherry picked from commit 07bf921)
jufajardini pushed a commit to jufajardini/suricata that referenced this pull request May 17, 2022
Set correct direction for PORT mode, where the server connects
to the client.

The direction is not also strictly enforced. No data in the wrong
direction will be accepted to setup the file or to be added to the
file after setup.

This also fixes files getting closed twice.

Adds some general cleanups.

Bug: OISF#3542.
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.

1 participant