Page MenuHomeFreeBSD

security/vuxml: Mark bro < 2.5.5 as vulnerable

Authored by leres on Aug 29 2018, 10:24 PM.



Proposed commit message:

Mark bro < 2.5.5 as vulnerable as per:

Reviewed by: ? (mentor)
Approved by: ? (mentor)
Differential Revision: ?

Diff Detail

rP FreeBSD ports repository
No Linters Available
No Unit Test Coverage
Build Status
Buildable 19276
Build 18889: arc lint + arc unit

Event Timeline

leres created this revision.Aug 29 2018, 10:24 PM
matthew added inline comments.Aug 29 2018, 10:40 PM

Who is reporting here?


These paragraphs have rather excessively long line lengths -- doesn't make validate warn you about the formatting here? Also, you can use any HTML elements inside the <blockquote> area, not just <p></p> -- so <ul><li></li></ul> could be pasted in directly from the BRO news page, although you will have to trim the CSS class settings.

leres updated this revision to Diff 47462.Aug 29 2018, 10:54 PM
leres marked 2 inline comments as done.

Address mat@'s comments
Populate "reports" and reformat the description.

Here's an update, please let me know if the <li> guys are formatted ok (I found examples that formatted the way I did but also some that indented multi line<li>'s).


Good point (but I'm disappointed validate didn't complain...)


make validate did not complain about the line length. Also I used really long lines the last time I added a entry for bro to security/vuxml and was trying to use it as a template. And I'm sure I used long lines because I found old entries that did it that way.

Using <ul> seems much better.

matthew accepted this revision.Aug 29 2018, 11:07 PM



validate only checks for well-formed XML, not semantic correctness.


Hmmm.... AFAIR the indentation style preferred by the project looks like:

    <li>"Weird" events are now generally suppressed/sampled
      by default according to some tunable parameters.</li>
    <li>Improved handling of empty lines in several text
      protocol analyzers that can cause performance issues
      when seen in long sequences.</li>
    <li>Add `smtp_excessive_pending_cmds' weird which
      serves as a notification for when the "pending command"
      queue has reached an upper limit and been cleared to
      prevent one from attempting to slowly exhaust

although I see this has not been rigorously observed. I guess if make validate doesn't complain then you're golden.

This revision is now accepted and ready to land.Aug 29 2018, 11:07 PM
leres updated this revision to Diff 47464.Aug 29 2018, 11:20 PM

No reason not to format the description using the preferred style.

I thought make validate did a bit more checking but I guess it
detects when you don't fill in a field (e.g. <name>) because the
optimized version of <name></name> is </name> which causes the
"tidy" version to be different.

This revision now requires review to proceed.Aug 29 2018, 11:20 PM
ler accepted this revision.Aug 29 2018, 11:58 PM

Ship it.

This revision is now accepted and ready to land.Aug 29 2018, 11:58 PM
leres closed this revision.Sep 22 2018, 4:11 PM

This seems to always happens with MFH. My new theory is that I need to populate the "Differential Revision" for both the commit (which I did) and with MFH commit (which I did not).