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

Fixes/nfs files/v1 #5201

Closed
wants to merge 3 commits into from
Closed

Conversation

victorjulien
Copy link
Member

In case of lossy connections the NFS state would properly clean up
transactions, including file transactions. However for files the
state was never set to 'truncated', leading to files to stay 'active'.

This would lead these files staying in the NFS's state. In long running
sessions with lots of files this would lead to performance and memory
use issues.

This patch cleans truncates the file that was being transmitted when
a file transaction is being closed.

Based on 65e9a7c
@victorjulien victorjulien requested a review from jasonish as a code owner July 20, 2020 13:23
This was referenced Jul 21, 2020
@victorjulien
Copy link
Member Author

Merged in #5207

@victorjulien victorjulien deleted the fixes/nfs-files/v1 branch August 31, 2020 12:16
jasonish added a commit to jasonish/suricata that referenced this pull request Mar 22, 2022
Fix parsing of content like "|aa b cc|" which was parsed as "|aa bc|"
without error or warning. This will now fail out, requiring all hex
values to be 2 chars.

Ticket OISF#5201
jasonish added a commit to jasonish/suricata that referenced this pull request Mar 22, 2022
Fix parsing of content like "|aa b cc|" which was parsed as "|aa bc|"
without error or warning. This will now fail out, requiring all hex
values to be 2 chars.

Ticket OISF#5201
jasonish added a commit to jasonish/suricata that referenced this pull request Mar 22, 2022
Fix parsing of content like "|aa b cc|" which was parsed as "|aa bc|"
without error or warning. This will now fail out, requiring all hex
values to be 2 chars.

Ticket OISF#5201
jasonish added a commit to jasonish/suricata that referenced this pull request Mar 23, 2022
Fix parsing of content like "|aa b cc|" which was parsed as "|aa bc|"
without error or warning. This will now fail out, requiring all hex
values to be 2 chars.

Ticket OISF#5201
victorjulien pushed a commit to victorjulien/suricata that referenced this pull request Mar 25, 2022
Fix parsing of content like "|aa b cc|" which was parsed as "|aa bc|"
without error or warning. This will now fail out, requiring all hex
values to be 2 chars.

Ticket OISF#5201
victorjulien pushed a commit to victorjulien/suricata that referenced this pull request Mar 25, 2022
Fix parsing of content like "|aa b cc|" which was parsed as "|aa bc|"
without error or warning. This will now fail out, requiring all hex
values to be 2 chars.

Ticket OISF#5201
jlucovsky pushed a commit to jlucovsky/suricata that referenced this pull request Apr 18, 2022
Fix parsing of content like "|aa b cc|" which was parsed as "|aa bc|"
without error or warning. This will now fail out, requiring all hex
values to be 2 chars.

Ticket OISF#5201

(cherry picked from commit 8d1e4a1)
victorjulien pushed a commit to victorjulien/suricata that referenced this pull request Apr 19, 2022
Fix parsing of content like "|aa b cc|" which was parsed as "|aa bc|"
without error or warning. This will now fail out, requiring all hex
values to be 2 chars.

Ticket OISF#5201

(cherry picked from commit 8d1e4a1)
catenacyber pushed a commit to catenacyber/suricata that referenced this pull request Jun 7, 2022
Add a rule with incomplete hex, for example "|22 2 22|" which
should result in a parse error.

Ticket OISF#5201.
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