metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JonZeolla <...@git.apache.org>
Subject [GitHub] metron pull request #805: METRON-1261: Apply bro security patch
Date Wed, 18 Oct 2017 13:33:07 GMT
GitHub user JonZeolla opened a pull request:

    https://github.com/apache/metron/pull/805

    METRON-1261: Apply bro security patch

    ## Contributor Comments
    This should update the version of bro that is auto-installed by full-dev/quick-dev, and
update some manual instructions for setting up bro, to use bro 2.4.2, which recently had a
security patch applied ([details](http://mailman.icsi.berkeley.edu/pipermail/bro/2017-October/012606.html)
[here](http://blog.bro.org/2017/10/bro-252-242-release-security-update.html)).  
    
    Additional testing instructions coming soon.
    
    
    ## Pull Request Checklist
    
    Thank you for submitting a contribution to Apache Metron.  
    Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
for complete smoke testing guides.  
    
    
    In order to streamline the review of the contribution we ask you follow these guidelines
and ask you to double check the following:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at
[Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).

    - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are
trying to resolve? Pay particular attention to the hyphen "-" character.
    - [x] Has your PR been rebased against the latest commit within the target branch (typically
master)?
    
    
    ### For code changes:
    - [ ] Have you included steps or a guide to how the change may be verified and tested
manually?
    - [ ] Have you verified the basic functionality of the build by building and running locally
with Vagrant full-dev environment or the equivalent?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered
by building and verifying the site-book? If not then run the following commands and the verify
changes via `site-book/target/site/index.html`:
    
      ```
      cd site-book
      mvn site
      ```
    
    #### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible.
    It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal
repository such that your branches are built there before submitting a pull request.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/JonZeolla/metron METRON-1261

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metron/pull/805.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #805
    
----
commit d39b72eaacba805703256f30b0e5ddc72e88599a
Author: Jon Zeolla <zeolla@gmail.com>
Date:   2017-10-18T13:08:21Z

    METRON-1261: Apply bro security patch

----


---

Mime
View raw message