[
https://bro-tracker.atlassian.net/browse/BIT-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003#comment-16003
]
Robin Sommer commented on BIT-1142:
-----------------------------------
I'm fine merging this but I would then still like to have an snmp.log for 2.3
...
> SNMP Analysis
> -------------
>
> Key: BIT-1142
> URL: https://bro-tracker.atlassian.net/browse/BIT-1142
> Project: Bro Issue Tracker
> Issue Type: New Feature
> Components: BinPAC, Bro
> Affects Versions: git/master
> Reporter: Jon Siwek
> Assignee: Seth Hall
> Fix For: 2.3
>
>
> /topic/jsiwek/snmp in bro, binpac, and bro-testing-private adds support for
> parsing SNMP datagrams. It's only absent a snmp.log.
> Seth, do you mind taking a look at what might make sense for a default
> snmp.log? I'm guessing it might look similar in concept to dns.log. A
> difference is I'm not sure how meaningful raw OID to value mappings will be.
> The code is in a merge-able state as it is in the branch/repos I mentioned,
> and IMO, has value even without a default snmp.log. So if you just want to
> flip to a merge request and postpone thinking up an snmp.log for later, I
> think that's fine, too.
--
This message was sent by Atlassian JIRA
(v6.3-OD-01-067#6307)
_______________________________________________
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
