Project

General

Profile

Actions
Copy link

Bug #5072

closed

detect/ip_proto: inconsistent behavior when specifying protocol by string

Added by Victor Julien almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jeff Lucovsky
Target version:
TBD
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 5.0, Needs backport to 6.0

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 3 (0 open — 3 closed)

Related to Suricata - Bug #4267: output: don't use /etc/protocolsClosedJeff LucovskyActions
Copied to Suricata - Bug #5114: detect/ip_proto: inconsistent behavior when specifying protocol by stringClosedShivani BhardwajActions
Copied to Suricata - Bug #5115: detect/ip_proto: inconsistent behavior when specifying protocol by stringClosedJeff LucovskyActions
Actions
Copy link
 #1

Updated by Jeff Lucovsky almost 3 years ago

  • Status changed from New to Assigned
  • Assignee changed from OISF Dev to Jeff Lucovsky
Actions
Copy link
 #2

Updated by Jeff Lucovsky almost 3 years ago

  • Related to Bug #4267: output: don't use /etc/protocols added
Actions
Copy link
 #3

Updated by Jeff Lucovsky almost 3 years ago

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

Updated by Jeff Lucovsky almost 3 years ago

  • Copied to Bug #5114: detect/ip_proto: inconsistent behavior when specifying protocol by string added
Actions
Copy link
 #5

Updated by Jeff Lucovsky almost 3 years ago

  • Copied to Bug #5115: detect/ip_proto: inconsistent behavior when specifying protocol by string added
Actions
Copy link
 #6

Updated by Jeff Lucovsky over 2 years ago

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: Atom PDF