Authenticating serialized data for safety and peace of mind

2016-07-22 Thread Jacob Wilder
Given that deserialization attacks are a ripe attack surface it's a good idea to make it possible to authenticate serialized objects whenever possible. In the case of Pirk—where systems which hold sensitive data will be

[GitHub] incubator-pirk issue #19: PIRK-10: Upgrade and Enforce Java 8

2016-07-22 Thread smarthi
Github user smarthi commented on the issue: https://github.com/apache/incubator-pirk/pull/19 This is good to merge now. It enforces Java 8 and Maven 3.3.9 as also RAT checks for license headers. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] incubator-pirk issue #19: PIRK-10: Upgrade and Enforce Java 8

2016-07-22 Thread ellisonanne
Github user ellisonanne commented on the issue: https://github.com/apache/incubator-pirk/pull/19 +1 Thanks adding back in the rat check. --- 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

Re: Minimum Maven version

2016-07-22 Thread Suneel Marthi
That fixed it Joe, it was those XML parser warnings that were failing RAT. We are indeed good now. Thanks again. On Fri, Jul 22, 2016 at 10:16 PM, Joe Witt wrote: > If you go here >https://travis-ci.org/apache/incubator-pirk > > You can then click on 'build history' >

Re: Minimum Maven version

2016-07-22 Thread Joe Witt
If you go here https://travis-ci.org/apache/incubator-pirk You can then click on 'build history' https://travis-ci.org/apache/incubator-pirk/builds You can then look for the failed/master build which mentions rat https://travis-ci.org/apache/incubator-pirk/builds/145628437 Then click the

Re: Minimum Maven version

2016-07-22 Thread Suneel Marthi
how do i access that? On Fri, Jul 22, 2016 at 10:05 PM, Joe Witt wrote: > Did you look in /home/travis/build/apache/incubator-pirk/target/rat.txt? > > The RAT reports are generally pretty good I have found. > > On Fri, Jul 22, 2016 at 10:04 PM, Suneel Marthi

Re: RTC/CTR Discussion

2016-07-22 Thread Josh Elser
I lean towards just needing a +1 to commit and still doing that myself. Just need to be clear however is decided. Ellison Anne Williams wrote: I don't see point in having to get a +1 from another committer for fixing trivial items such as merge conflicts, build breaks, etc. I also would

Re: Minimum Maven version

2016-07-22 Thread Joe Witt
Did you look in /home/travis/build/apache/incubator-pirk/target/rat.txt? The RAT reports are generally pretty good I have found. On Fri, Jul 22, 2016 at 10:04 PM, Suneel Marthi wrote: > Could it be that the .travis.yml needs a license header, that's the only > one

Re: Minimum Maven version

2016-07-22 Thread Suneel Marthi
Could it be that the .travis.yml needs a license header, that's the only one without a header. On Fri, Jul 22, 2016 at 9:41 PM, Joe Witt wrote: > Suneel > > It is probably a good idea to keep it there because it can really help > with automating some of the checks as

Re: JIRA key names in summary

2016-07-22 Thread Ellison Anne Williams
The repetitive issue number in the title is a silly (bad) habit of mine - I will try to break it now... :) On Fri, Jul 22, 2016 at 1:57 PM, Suneel Marthi wrote: > I agree its redundant to have the Jira in the Summary line. > > Also when committing PRs against a jira, the

Re: Minimum Maven version

2016-07-22 Thread Joe Witt
Suneel It is probably a good idea to keep it there because it can really help with automating some of the checks as people put in PRs. I'm happy to help do licensing/header hunting soon. Thanks Joe On Fri, Jul 22, 2016 at 6:53 PM, Suneel Marthi wrote: > We r good now,

[GitHub] incubator-pirk issue #19: PIRK-10: Upgrade and Enforce Java 8

2016-07-22 Thread smarthi
Github user smarthi commented on the issue: https://github.com/apache/incubator-pirk/pull/19 This PR is good to go, The travis build now runs with maven 3.3.9 and Java 8. Disabled rat check temporarily to get past travis build failures. --- If your project is set up for it, you can

Re: Minimum Maven version

2016-07-22 Thread Suneel Marthi
We r good now, I disabled the rat check to get past the build failure, i guess we don't need that for travis, do we? On Fri, Jul 22, 2016 at 6:19 PM, Suneel Marthi wrote: > Getting a travis build error for RAT, any ideas ? I am not seeing this > locally. > > [ERROR]

Re: Minimum Maven version

2016-07-22 Thread Suneel Marthi
Getting a travis build error for RAT, any ideas ? I am not seeing this locally. [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project pirk: Too many files with unapproved license: 1 See RAT report in:

Re: Minimum Maven version

2016-07-22 Thread Suneel Marthi
... I am also gonna disable Jdk 7 jobs on travis as part of this change. OK with @here ? On Fri, Jul 22, 2016 at 6:01 PM, Suneel Marthi wrote: > Let's go with Option 1, i can modify .travis.yml to account for Maven 3.3x > > On Fri, Jul 22, 2016 at 5:58 PM, Tim

Fwd: [jira] [Commented] (PIRK-1) Initial Pirk Code

2016-07-22 Thread Walter Ray-Dulany
Seems ripe for closing. On Fri, Jul 22, 2016 at 11:58 AM, Tim Ellison (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/PIRK-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389735#comment-15389735 > ] > > Tim Ellison commented on PIRK-1: