Re: Packet capture support for Windows environment.

[James Sirota]

I don't off the top of my head, but if you file a Jira and have it hang out 
there for a week or so am sure someone will turn up.  New people are looking at 
Metron every day and a lot of them run on Windows.  It would also help to start 
a discussion thread outlining what specifically you are wanting to accomplish 
and link it to the Jira you created.  Give some time and if you don't find 
anyone to work on it with you we'll circle back and figure out the next steps. 

31.05.2016, 17:01, "Jimson K James" :
> Hi James,
>
> Thank you. That's bit more promising.
>
> Will create a JIRA ticket for the feasibility of Windows support.
>
> Do you know any one who will be interested in Metron supporting Windows
> packet captures (even as an experimental setup or for testing inside VMs) ?
>
> On Tuesday, 31 May 2016, James Sirota  wrote:
>
>>  Hi Jimson,
>>
>>  Nick is correct. We don't support Windows at this time. With this said,
>>  you may want to file a Jira to add it. A few community members may share
>>  you need to run PCAP capture on windows and can create this capability for
>>  us
>>
>>  31.05.2016, 07:05, "Nick Allen" >:
>>  > Sorry, but we do not support Windows.
>>  >
>>  > On Sun, May 29, 2016 at 7:34 PM, Jimson K James >  >
>>  > wrote:
>>  >
>>  >> Hi Metron Team,
>>  >>
>>  >> Do we have any official support for packet capture from Windows based
>>  >> machines?
>>  >> As of now DPDK donot have Windows support. Of course I can use pcapy
>>  with
>>  >> WinPcap, but is that the only solution?
>>  >>
>>  >> Looks like if we can bring the Windows packet into the picture that
>>  would
>>  >> be cool.
>>  >>
>>  >> Please comment.
>>  >>
>>  >> Best Regards,
>>  >> J.
>>  >
>>  > --
>>  > Nick Allen >
>>
>>  ---
>>  Thank you,
>>
>>  James Sirota
>>  PPMC- Apache Metron (Incubating)
>>  jsirota AT apache DOT org

--- 
Thank you,

James Sirota
PPMC- Apache Metron (Incubating)
jsirota AT apache DOT org

Re: Packet capture support for Windows environment.

[Jimson K James]

Hi James,

Thank you. That's bit more promising.

Will create a JIRA ticket for the feasibility of Windows support.

Do you know any one who will be interested in Metron supporting Windows
packet captures (even as an experimental setup or for testing inside VMs) ?

On Tuesday, 31 May 2016, James Sirota  wrote:

> Hi Jimson,
>
> Nick is correct. We don't support Windows at this time.  With this said,
> you may want to file a Jira to add it.  A few community members may share
> you need to run PCAP capture on windows and can create this capability for
> us
>
> 31.05.2016, 07:05, "Nick Allen" >:
> > Sorry, but we do not support Windows.
> >
> > On Sun, May 29, 2016 at 7:34 PM, Jimson K James  >
> > wrote:
> >
> >>  Hi Metron Team,
> >>
> >>  Do we have any official support for packet capture from Windows based
> >>  machines?
> >>  As of now DPDK donot have Windows support. Of course I can use pcapy
> with
> >>  WinPcap, but is that the only solution?
> >>
> >>  Looks like if we can bring the Windows packet into the picture that
> would
> >>  be cool.
> >>
> >>  Please comment.
> >>
> >>  Best Regards,
> >>  J.
> >
> > --
> > Nick Allen >
>
> ---
> Thank you,
>
> James Sirota
> PPMC- Apache Metron (Incubating)
> jsirota AT apache DOT org
>

Re: Quick start deployment error

[James Sirota]

Hi Yazan,

We have a FAQ article on how to downgrade Ansible:
https://cwiki.apache.org/confluence/display/METRON/Downgrade+Ansible'

29.05.2016, 08:21, "Yazan Boshmaf" :
> Yes, it turns out I had a new version of Ansible. Downgrading to 2.0.0.2
> resolved the issues.
>
> Here's the direct link, which you might want to include in the README.md
> file: http://releases.ansible.com/ansible/ansible-2.0.0.2.tar.gz
>
> Thanks,
> Yazan
>
> On Sun, May 29, 2016 at 5:24 PM, Nick Allen  wrote:
>
>>  The issue is probably due to an unsupported version of Ansible. We have
>>  had more than a few issues trying to address bugs that get (re)introduced
>>  in different versions of Ansible.
>>
>>  Run the following script. Make sure that all of the versions match the
>>  supported versions defined in the README
>>  <
>>  
>> https://github.com/apache/incubator-metron/tree/master/metron-deployment/vagrant/quick-dev-platform#prerequisites
>>  >
>>  .
>>
>>  ./metron-deployment/scripts/platform-info.sh
>>
>>  If you're still having issues, send the output of that script to the
>>  mailing list so that we can help further.
>>
>>  Thanks!
>>
>>  On Sun, May 29, 2016 at 9:43 AM, Yazan Boshmaf  wrote:
>>
>>  > Hello!
>>  >
>>  > I'm going through the single-node deployment guide (
>>  >
>>  
>> https://github.com/apache/incubator-metron/tree/master/metron-deployment/vagrant/quick-dev-platform
>>  )
>>  > and the playbook fails at the following task. Any ideas?
>>  >
>>  > The main services seems to be up and running (see screen grab).
>>  Thanks![image:
>>  > Inline image 1]
>>  >
>>  > All the best,
>>  > Yazan
>>  >
>>  >
>>  >
>>  > TASK [elasticsearch : Add Elasticsearch templates for topologies]
>>  > **
>>  >
>>  > failed: [node1] (item={u'sensor': u'bro', u'file': {'mappings':
>>  > {'bro_doc': {'_timestamp': {'enabled': True}, 'properties':
>>  > {'enrichments:geo:ip_dst_addr:location_point': {'type': 'geo_point'},
>>  > 'timestamp': {'type': 'date', 'format': 'epoch_millis', 'template':
>>  > 'bro_index*'}}) => {"content": "", "content_length": "450",
>>  "content_type":
>>  > "application/json; charset=UTF-8", "failed": true, "item": {"file":
>>  > {"mappings": {"bro_doc": {"_timestamp": {"enabled": true}, "properties":
>>  > {"enrichments:geo:ip_dst_addr:location_point": {"type": "geo_point"},
>>  > "timestamp": {"format": "epoch_millis", "type": "date", "template":
>>  > "bro_index*"}, "sensor": "bro"}, "msg": "Status code was not [200]: HTTP
>>  > Error 400: Bad Request", "redirected": false, "status": 400, "url": "
>>  > http://node1:9200/_template/template_bro"}
>>  > failed: [node1] (item={u'sensor': u'yaf', u'file': {'mappings':
>>  > {'yaf_doc': {'_timestamp': {'enabled': True}, 'properties': {'uflags':
>>  > {'type': 'string'}, 'pkt': {'type': 'string'}, 'app': {'type': 'string'},
>>  > 'rtt': {'type': 'string'}, 'tag': {'type': 'string'}, 'duration':
>>  {'type':
>>  > 'string'}, 'riflags': {'type': 'string'}, 'sip': {'type': 'string'},
>>  > 'proto': {'type': 'string'}, 'rtag': {'type': 'string'}, 'oct': {'type':
>>  > 'string'}, 'risn': {'type': 'string'}, 'end-time': {'type': 'string'},
>>  > 'end-reason': {'type': 'string'}, 'timestamp': {'type': 'date', 'format':
>>  > 'epoch_millis'}, 'dp': {'type': 'string'},
>>  > 'enrichments:geo:ip_dst_addr:location_point': {'type': 'geo_point'},
>>  > 'roct': {'type': 'string'}, 'sp': {'type': 'string'}, 'iflags': {'type':
>>  > 'string'}, 'isn': {'type': 'string'}, 'ruflags': {'type': 'string'},
>>  > 'rpkt': {'type': 'string'}, 'dip': {'type': 'string', 'template':
>>  > 'yaf_index*'}}) => {"content": "", "content_length": "450",
>>  "content_type":
>>  > "application/json; charset=UTF-8", "failed": true, "item": {"file":
>>  > {"mappings": {"yaf_doc": {"_timestamp": {"enabled": true}, "properties":
>>  > {"app": {"type": "string"}, "dip": {"type": "string"}, "dp": {"type":
>>  > "string"}, "duration": {"type": "string"}, "end-reason": {"type":
>>  > "string"}, "end-time": {"type": "string"},
>>  > "enrichments:geo:ip_dst_addr:location_point": {"type": "geo_point"},
>>  > "iflags": {"type": "string"}, "isn": {"type": "string"}, "oct": {"type":
>>  > "string"}, "pkt": {"type": "string"}, "proto": {"type": "string"},
>>  > "riflags": {"type": "string"}, "risn": {"type": "string"}, "roct":
>>  {"type":
>>  > "string"}, "rpkt": {"type": "string"}, "rtag": {"type": "string"}, "rtt":
>>  > {"type": "string"}, "ruflags": {"type": "string"}, "sip": {"type":
>>  > "string"}, "sp": {"type": "string"}, "tag": {"type": "string"},
>>  > "timestamp": {"format": "epoch_millis", "type": "date"}, "uflags":
>>  {"type":
>>  > "string", "template": "yaf_index*"}, "sensor": "yaf"}, "msg": "Status
>>  > code was not [200]: HTTP Error 400: Bad Request", "redirected": false,
>>  > "status": 400, "url": "http://node1:9200/_template/template_yaf"}
>>  > failed: [node1] (item={u'sensor': u'snort', 

[GitHub] incubator-metron pull request: METRON-180 Enable each component to be instal...

[james-sirota]

Github user james-sirota commented on the pull request:

https://github.com/apache/incubator-metron/pull/133
  
@nickwallen what set of commands should i run to validate this?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-metron pull request: METRON-174 Storm consumption of hbase enrichm...

[james-sirota]

Github user james-sirota commented on the pull request:

https://github.com/apache/incubator-metron/pull/127
  
+ 1.  Had a kafka problem.  Works great 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Secure code analysis

[James Sirota]

Jon, would it be possible for you to scan Metron from your own branch?  I'd 
like to know if this is useful at all.  If we get value out of it I'll run this 
down and see how we can get it hooked up.

31.05.2016, 10:08, "Nick Allen" :
> I connect Travis to my own personal fork of Metron so that the CI builds
> run on my own branches before I submit PRs. Thinking you could do the same
> with this. Maybe I'm wrong.
>
> On Tue, May 31, 2016 at 1:06 PM, zeo...@gmail.com  wrote:
>
>>  To register project on Coverity Scan, you must be contributor or maintainer
>>  of the project.
>>
>>  It may also be worth mentioning that there are a ton of Apache projects
>>  already registered, including Ambari, Drill, Flume, Hadoop, HBase, NiFi,
>>  Oozie, Ranger, Sqoop, Spark, Storm, Tez, etc. See
>>  https://scan.coverity.com/projects?page=2
>>
>>  Jon
>>
>>  On Tue, May 31, 2016 at 12:52 PM Nick Allen  wrote:
>>
>>  > You could set it up on your own fork of Metron in Github. Then you can
>>  > tell us if it is useful at all.
>>  >
>>  > On Sat, May 28, 2016 at 2:36 PM, zeo...@gmail.com 
>>  > wrote:
>>  >
>>  > > So I did a bit of digging today and I found a few op
>>  > > tions, but so far my
>>  > > favourite is Coverity Scan .
>>  I've
>>  > > never used this product before, so I'm not exactly sure what to expect,
>>  > but
>>  > > I guess anyone can kick off a scan of an open source project and get
>>  > > results within 48 hours. I was in the process of registering Metron to
>>  > be
>>  > > scanned but I found some things in their scan user agreement which I
>>  > wasn't
>>  > > sure everybody would be in line with (see below for the excerpts -
>>  note I
>>  > > did NOT read the entire document and IANAL).
>>  > >
>>  > > Here's the TL;DR of what Coverity Scan is:
>>  > >
>>  > > Coverity Scan  is a free static code
>>  analysis
>>  > > tool for Java, C, C++, C# and JavaScript.
>>  > >
>>  > > This addon leverages the Travis-CI infrastructure to automatically run
>>  > code
>>  > > analysis on your GitHub projects.
>>  > >
>>  > > Coverity Scan is a service by which Coverity provides the results of
>>  > > analysis on open source coding projects to open source code developers
>>  > that
>>  > > have registered their products with Coverity Scan.
>>  > >
>>  > > Some examples of defects and vulnerabilities found by Coverity Quality
>>  > > Advisor include:
>>  > >
>>  > > - resources leaks
>>  > > - dereferences of NULL pointers
>>  > > - incorrect usage of APIs
>>  > > - use of uninitialized data
>>  > > - memory corruptions
>>  > > - buffer overruns
>>  > > - control flow issues
>>  > > - error handling issues
>>  > > - incorrect expressions
>>  > > - concurrency issues
>>  > > - insecure data handling
>>  > > - unsafe use of signed values
>>  > > - use of resources that have been freed
>>  > >
>>  > > Register your project with Coverity Scan by completing the project
>>  > > registration form found at scan.coverity.com. Upon your completion of
>>  > > project registration (including acceptance of the Scan User Agreement)
>>  > and
>>  > > your receipt of confirmation of registration of your project, you will
>>  be
>>  > > able to download the Software required to submit a build of your code
>>  for
>>  > > analysis by Coverity Scan. You may then download the Software,
>>  complete a
>>  > > build and submit your Registered Project build for analysis and review
>>  in
>>  > > Coverity Scan. Coverity Scan is only available for use with open source
>>  > > projects that are registered with Coverity Scan.
>>  > > Here are some interesting snippets from their scan user agreement:
>>  > >
>>  > > Your use of our software is acceptance of our Terms
>>  > > 
>>  > >
>>  > > You will not disassemble, decompile, reverse engineer, modify or create
>>  > > derivative works of Our Service, software products or documentation nor
>>  > > permit any third party to do so, except to the extent such restrictions
>>  > are
>>  > > prohibited by applicable mandatory local law
>>  > >
>>  > > You will not disclose to any third party any comparison of the results
>>  of
>>  > > operation of Our Service or software products with other services or
>>  > > products, except as expressly permitted by this Agreement
>>  > >
>>  > > You will not publish any findings regarding or resulting from use of
>>  the
>>  > > Service or the Software
>>  > >
>>  > > You agree that We may use Your name and logo (in a form approved by
>>  You)
>>  > > and Registered Product information to identify You and such project as
>>  a
>>  > > participant of Our Scan Program on Our website or in Our marketing or
>>  > > publicity materials or in any filings made in connection with state or
>>  > > federal securities laws.
>>  > >
>>  > > 

Re: Secure code analysis

[Nick Allen]

I connect Travis to my own personal fork of Metron so that the CI builds
run on my own branches before I submit PRs.  Thinking you could do the same
with this.  Maybe I'm wrong.

On Tue, May 31, 2016 at 1:06 PM, zeo...@gmail.com  wrote:

> To register project on Coverity Scan, you must be contributor or maintainer
> of the project.
>
> It may also be worth mentioning that there are a ton of Apache projects
> already registered, including Ambari, Drill, Flume, Hadoop, HBase, NiFi,
> Oozie, Ranger, Sqoop, Spark, Storm, Tez, etc.  See
> https://scan.coverity.com/projects?page=2
>
> Jon
>
> On Tue, May 31, 2016 at 12:52 PM Nick Allen  wrote:
>
> > You could set it up on your own fork of Metron in Github.  Then you can
> > tell us if it is useful at all.
> >
> > On Sat, May 28, 2016 at 2:36 PM, zeo...@gmail.com 
> > wrote:
> >
> > > So I did a bit of digging today and I found a few op
> > > tions, but so far my
> > > favourite is Coverity Scan .
> I've
> > > never used this product before, so I'm not exactly sure what to expect,
> > but
> > > I guess anyone can kick off a scan of an open source project and get
> > > results within 48 hours.  I was in the process of registering Metron to
> > be
> > > scanned but I found some things in their scan user agreement which I
> > wasn't
> > > sure everybody would be in line with (see below for the excerpts -
> note I
> > > did NOT read the entire document and IANAL).
> > >
> > > Here's the TL;DR of what Coverity Scan is:
> > >
> > > Coverity Scan  is a free static code
> analysis
> > > tool for Java, C, C++, C# and JavaScript.
> > >
> > > This addon leverages the Travis-CI infrastructure to automatically run
> > code
> > > analysis on your GitHub projects.
> > >
> > > Coverity Scan is a service by which Coverity provides the results of
> > > analysis on open source coding projects to open source code developers
> > that
> > > have registered their products with Coverity Scan.
> > >
> > > Some examples of defects and vulnerabilities found by Coverity Quality
> > > Advisor include:
> > >
> > >- resources leaks
> > >- dereferences of NULL pointers
> > >- incorrect usage of APIs
> > >- use of uninitialized data
> > >- memory corruptions
> > >- buffer overruns
> > >- control flow issues
> > >- error handling issues
> > >- incorrect expressions
> > >- concurrency issues
> > >- insecure data handling
> > >- unsafe use of signed values
> > >- use of resources that have been freed
> > >
> > > Register your project with Coverity Scan by completing the project
> > > registration form found at scan.coverity.com. Upon your completion of
> > > project registration (including acceptance of the Scan User Agreement)
> > and
> > > your receipt of confirmation of registration of your project, you will
> be
> > > able to download the Software required to submit a build of your code
> for
> > > analysis by Coverity Scan. You may then download the Software,
> complete a
> > > build and submit your Registered Project build for analysis and review
> in
> > > Coverity Scan. Coverity Scan is only available for use with open source
> > > projects that are registered with Coverity Scan.
> > > Here are some interesting snippets from their scan user agreement:
> > >
> > > Your use of our software is acceptance of our Terms
> > > 
> > >
> > > You will not disassemble, decompile, reverse engineer, modify or create
> > > derivative works of Our Service, software products or documentation nor
> > > permit any third party to do so, except to the extent such restrictions
> > are
> > > prohibited by applicable mandatory local law
> > >
> > > You will not disclose to any third party any comparison of the results
> of
> > > operation of Our Service or software products with other services or
> > > products, except as expressly permitted by this Agreement
> > >
> > > You will not publish any findings regarding or resulting from use of
> the
> > > Service or the Software
> > >
> > > You agree that We may use Your name and logo (in a form approved by
> You)
> > > and Registered Product information to identify You and such project as
> a
> > > participant of Our Scan Program on Our website or in Our marketing or
> > > publicity materials or in any filings made in connection with state or
> > > federal securities laws.
> > >
> > > Additionally, upon execution of this Agreement, the parties will use
> > > commercially reasonable efforts to issue mutually agreed upon joint
> press
> > > releases or other public communications announcing Your entry into this
> > > Agreement.
> > >
> > > At Our written request, You will furnish Us with (a) a certification
> > signed
> > > by an officer of Your company providing user or access information that
> > > identifies whether 

Re: Secure code analysis

[zeo...@gmail.com]

To register project on Coverity Scan, you must be contributor or maintainer
of the project.

It may also be worth mentioning that there are a ton of Apache projects
already registered, including Ambari, Drill, Flume, Hadoop, HBase, NiFi,
Oozie, Ranger, Sqoop, Spark, Storm, Tez, etc.  See
https://scan.coverity.com/projects?page=2

Jon

On Tue, May 31, 2016 at 12:52 PM Nick Allen  wrote:

> You could set it up on your own fork of Metron in Github.  Then you can
> tell us if it is useful at all.
>
> On Sat, May 28, 2016 at 2:36 PM, zeo...@gmail.com 
> wrote:
>
> > So I did a bit of digging today and I found a few op
> > tions, but so far my
> > favourite is Coverity Scan .  I've
> > never used this product before, so I'm not exactly sure what to expect,
> but
> > I guess anyone can kick off a scan of an open source project and get
> > results within 48 hours.  I was in the process of registering Metron to
> be
> > scanned but I found some things in their scan user agreement which I
> wasn't
> > sure everybody would be in line with (see below for the excerpts - note I
> > did NOT read the entire document and IANAL).
> >
> > Here's the TL;DR of what Coverity Scan is:
> >
> > Coverity Scan  is a free static code analysis
> > tool for Java, C, C++, C# and JavaScript.
> >
> > This addon leverages the Travis-CI infrastructure to automatically run
> code
> > analysis on your GitHub projects.
> >
> > Coverity Scan is a service by which Coverity provides the results of
> > analysis on open source coding projects to open source code developers
> that
> > have registered their products with Coverity Scan.
> >
> > Some examples of defects and vulnerabilities found by Coverity Quality
> > Advisor include:
> >
> >- resources leaks
> >- dereferences of NULL pointers
> >- incorrect usage of APIs
> >- use of uninitialized data
> >- memory corruptions
> >- buffer overruns
> >- control flow issues
> >- error handling issues
> >- incorrect expressions
> >- concurrency issues
> >- insecure data handling
> >- unsafe use of signed values
> >- use of resources that have been freed
> >
> > Register your project with Coverity Scan by completing the project
> > registration form found at scan.coverity.com. Upon your completion of
> > project registration (including acceptance of the Scan User Agreement)
> and
> > your receipt of confirmation of registration of your project, you will be
> > able to download the Software required to submit a build of your code for
> > analysis by Coverity Scan. You may then download the Software, complete a
> > build and submit your Registered Project build for analysis and review in
> > Coverity Scan. Coverity Scan is only available for use with open source
> > projects that are registered with Coverity Scan.
> > Here are some interesting snippets from their scan user agreement:
> >
> > Your use of our software is acceptance of our Terms
> > 
> >
> > You will not disassemble, decompile, reverse engineer, modify or create
> > derivative works of Our Service, software products or documentation nor
> > permit any third party to do so, except to the extent such restrictions
> are
> > prohibited by applicable mandatory local law
> >
> > You will not disclose to any third party any comparison of the results of
> > operation of Our Service or software products with other services or
> > products, except as expressly permitted by this Agreement
> >
> > You will not publish any findings regarding or resulting from use of the
> > Service or the Software
> >
> > You agree that We may use Your name and logo (in a form approved by You)
> > and Registered Product information to identify You and such project as a
> > participant of Our Scan Program on Our website or in Our marketing or
> > publicity materials or in any filings made in connection with state or
> > federal securities laws.
> >
> > Additionally, upon execution of this Agreement, the parties will use
> > commercially reasonable efforts to issue mutually agreed upon joint press
> > releases or other public communications announcing Your entry into this
> > Agreement.
> >
> > At Our written request, You will furnish Us with (a) a certification
> signed
> > by an officer of Your company providing user or access information that
> > identifies whether the Service and the Software is being used in
> accordance
> > with the terms of this Agreement, and (b) log files from any License
> > Manager. Upon at least thirty (30) days prior written notice, We may
> > engage, at Our expense, an independent auditor to audit Your use of the
> > Service and the Software to ensure that You are in compliance with the
> > terms of this Agreement. ... You will provide the auditor with access to
> > the relevant records and facilities.
> >
> > Jon

Re: Secure code analysis

[Nick Allen]

You could set it up on your own fork of Metron in Github.  Then you can
tell us if it is useful at all.

On Sat, May 28, 2016 at 2:36 PM, zeo...@gmail.com  wrote:

> So I did a bit of digging today and I found a few op
> tions, but so far my
> favourite is Coverity Scan .  I've
> never used this product before, so I'm not exactly sure what to expect, but
> I guess anyone can kick off a scan of an open source project and get
> results within 48 hours.  I was in the process of registering Metron to be
> scanned but I found some things in their scan user agreement which I wasn't
> sure everybody would be in line with (see below for the excerpts - note I
> did NOT read the entire document and IANAL).
>
> Here's the TL;DR of what Coverity Scan is:
>
> Coverity Scan  is a free static code analysis
> tool for Java, C, C++, C# and JavaScript.
>
> This addon leverages the Travis-CI infrastructure to automatically run code
> analysis on your GitHub projects.
>
> Coverity Scan is a service by which Coverity provides the results of
> analysis on open source coding projects to open source code developers that
> have registered their products with Coverity Scan.
>
> Some examples of defects and vulnerabilities found by Coverity Quality
> Advisor include:
>
>- resources leaks
>- dereferences of NULL pointers
>- incorrect usage of APIs
>- use of uninitialized data
>- memory corruptions
>- buffer overruns
>- control flow issues
>- error handling issues
>- incorrect expressions
>- concurrency issues
>- insecure data handling
>- unsafe use of signed values
>- use of resources that have been freed
>
> Register your project with Coverity Scan by completing the project
> registration form found at scan.coverity.com. Upon your completion of
> project registration (including acceptance of the Scan User Agreement) and
> your receipt of confirmation of registration of your project, you will be
> able to download the Software required to submit a build of your code for
> analysis by Coverity Scan. You may then download the Software, complete a
> build and submit your Registered Project build for analysis and review in
> Coverity Scan. Coverity Scan is only available for use with open source
> projects that are registered with Coverity Scan.
> Here are some interesting snippets from their scan user agreement:
>
> Your use of our software is acceptance of our Terms
> 
>
> You will not disassemble, decompile, reverse engineer, modify or create
> derivative works of Our Service, software products or documentation nor
> permit any third party to do so, except to the extent such restrictions are
> prohibited by applicable mandatory local law
>
> You will not disclose to any third party any comparison of the results of
> operation of Our Service or software products with other services or
> products, except as expressly permitted by this Agreement
>
> You will not publish any findings regarding or resulting from use of the
> Service or the Software
>
> You agree that We may use Your name and logo (in a form approved by You)
> and Registered Product information to identify You and such project as a
> participant of Our Scan Program on Our website or in Our marketing or
> publicity materials or in any filings made in connection with state or
> federal securities laws.
>
> Additionally, upon execution of this Agreement, the parties will use
> commercially reasonable efforts to issue mutually agreed upon joint press
> releases or other public communications announcing Your entry into this
> Agreement.
>
> At Our written request, You will furnish Us with (a) a certification signed
> by an officer of Your company providing user or access information that
> identifies whether the Service and the Software is being used in accordance
> with the terms of this Agreement, and (b) log files from any License
> Manager. Upon at least thirty (30) days prior written notice, We may
> engage, at Our expense, an independent auditor to audit Your use of the
> Service and the Software to ensure that You are in compliance with the
> terms of this Agreement. ... You will provide the auditor with access to
> the relevant records and facilities.
>
> Jon
>
> On Fri, May 27, 2016 at 11:14 AM zeo...@gmail.com 
> wrote:
>
> > There's nothing built-in with Travis, but we could install a tool to do
> > this as part of the installation of tools on the build box.  I'm gonna
> > reach out to people in my local circle who specialize in secure code
> > analysis and see what all of the options are.
> >
> > Jon
> >
> > On Fri, May 27, 2016 at 9:50 AM Nick Allen  wrote:
> >
> >> I completely agree that we will need some focus on this.
> >>
> >> What could Travis do for us?  I wasn't aware that they offered security
> >> scanning.

Re: Platform and UI Requirements Meeting

[Kumar, Deeptaanshu]

Hi Houshang,

Several members of our UI team at Capital One want to be included in these
weekly meetings. Is there a meeting invite that I can forward to them?

Sincerely,

Deeptaanshu Kumar
EDS ­ ISRM 
Data Engineer
deeptaanshu.ku...@capitalone.com





On 5/30/16, 5:17 PM, "Houshang Livian"  wrote:

>Hello Everyone,
>
>Just a reminder that there is a weekly UI Discussion on Thursdays at 10AM
>CST.
>
>This weeks topic will be Navigation
>
>
>Houshang Livian
>Senior User Experience Designer
>Hortonworks
>
>www.hortonworks.com
>
>
>Mobile: (831) 521-4176
>hliv...@hortonworks.com
>
>



The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.

Re: Packet capture support for Windows environment.

[Nick Allen]

Sorry, but we do not support Windows.

On Sun, May 29, 2016 at 7:34 PM, Jimson K James 
wrote:

> Hi Metron Team,
>
> Do we have any official support for packet capture from Windows based
> machines?
> As of now DPDK donot have Windows support. Of course I can use pcapy with
> WinPcap, but is that the only solution?
>
> Looks like if we can bring the Windows packet into the picture that would
> be cool.
>
> Please comment.
>
> Best Regards,
> J.
>



-- 
Nick Allen 

[GitHub] incubator-metron pull request: METRON-174 Storm consumption of hba...

[cestella]

Github user cestella commented on the pull request:

https://github.com/apache/incubator-metron/pull/127#issuecomment-222638653
  
You sure Kafka is still up?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---