Bug #3339
closed
Missing community ID in smb, rdp, tftp, dhcp
Added by Eric Leblond about 5 years ago.
Updated over 4 years ago.
Label:
Needs backport to 5.0
Description
The function JsonAddCommonOptions is not called in SMB, RDP, TFTP and DHCP protocols resulting in Community ID not to be present even if asked.
In the case of SMB and RDP this is clearly missing. For TFTP and DHCP, this could be discussed as we have no real flow. But other tools should be able to build the same community ID so it seems ok to have it.
- Assignee set to Eric Leblond
- Target version set to 70
- Assignee changed from Eric Leblond to OISF Dev
- Priority changed from Normal to High
fileinfo is also affected (5.0.3). Any chance of this making it as a separate PR?
- Status changed from New to In Review
- Assignee changed from OISF Dev to Jeff Lucovsky
- Label Needs backport to 5.0 added
- Target version changed from 70 to 6.0.0beta1
- Copied to Bug #3804: Missing community ID in smb, rdp, tftp, dhcp added
- Status changed from In Review to Closed
- Copied to Bug #3810: Missing community ID in smb, rdp, tftp, dhcp added
Also available in: Atom
PDF