Project

General

Profile

Actions
Copy link

Bug #5115

closed

detect/ip_proto: inconsistent behavior when specifying protocol by string

Added by Jeff Lucovsky about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jeff Lucovsky
Target version:
5.0.9
Affected Versions:
Effort:
Difficulty:
Label:

Description

ip_proto:TCP will use getprotobyname, which may not work depending on the OS. E.g. in a docker Alpine it fails. We should probably just use a built-in table.

Related issues 1 (0 open — 1 closed)

Copied from Suricata - Bug #5072: detect/ip_proto: inconsistent behavior when specifying protocol by stringClosedJeff LucovskyActions
Actions
Copy link
 #1

Updated by Jeff Lucovsky about 2 years ago

  • Copied from Bug #5072: detect/ip_proto: inconsistent behavior when specifying protocol by string added
Actions
Copy link
 #2

Updated by Jeff Lucovsky about 2 years ago

  • Status changed from Assigned to In Progress

Cherry-pick commit(s)
- e77e8dbe18bdb70e42713abe4e90ec724adab5ca
- 5cb996efcf2248a6a04abfe2bde1dc5115bdfac2
- 1e2883602b8d95d96fa9c31e5ebbcb68ceeaa14a
- ff0cf89738d7b947a3d7d8d0c6c5dc7adb95e6af
- b52496725771c0a4bc98e1fe5c246bca77e8da03
- 3bd1d258a98c7e6f6fa45feb111f3297f1a527e7
- 4f2f745bed4858c6441b1b936f66453e87b715bb

Actions
Copy link
 #3

Updated by Jeff Lucovsky about 2 years ago

  • Status changed from In Progress to In Review
Actions
Copy link
 #4

Updated by Jeff Lucovsky about 2 years ago

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: Atom PDF