Return-Path: X-Original-To: apmail-struts-commits-archive@minotaur.apache.org Delivered-To: apmail-struts-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3692711600 for ; Sat, 7 Jun 2014 09:41:25 +0000 (UTC) Received: (qmail 40824 invoked by uid 500); 7 Jun 2014 09:41:25 -0000 Delivered-To: apmail-struts-commits-archive@struts.apache.org Received: (qmail 40785 invoked by uid 500); 7 Jun 2014 09:41:25 -0000 Mailing-List: contact commits-help@struts.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@struts.apache.org Delivered-To: mailing list commits@struts.apache.org Received: (qmail 40778 invoked by uid 99); 7 Jun 2014 09:41:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jun 2014 09:41:24 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jun 2014 09:41:23 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id B327C23889ED for ; Sat, 7 Jun 2014 09:41:03 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r911689 - in /websites/production/struts/content: index.html submitting-patches.html Date: Sat, 07 Jun 2014 09:41:03 -0000 To: commits@struts.apache.org From: lukaszlenart@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20140607094103.B327C23889ED@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: lukaszlenart Date: Sat Jun 7 09:41:03 2014 New Revision: 911689 Log: Updates production Modified: websites/production/struts/content/index.html websites/production/struts/content/submitting-patches.html Modified: websites/production/struts/content/index.html ============================================================================== --- websites/production/struts/content/index.html (original) +++ websites/production/struts/content/index.html Sat Jun 7 09:41:03 2014 @@ -129,9 +129,10 @@ Version notes
-

Struts up to 2.3.16.1: Zero-Day Exploit Mitigation!

-

In Struts 2.3.16.1, an issue with ClassLoader manipulation via request parameters was supposed to be resolved. Unfortunately, - the correction wasn't sufficient, read more +

Google's Patch Rewards program

+

During SFHTML5 Google announced that they extend their program + to cover the Apache Struts project as well. Now you can earn some many preparing patches for us! + read more

Modified: websites/production/struts/content/submitting-patches.html ============================================================================== --- websites/production/struts/content/submitting-patches.html (original) +++ websites/production/struts/content/submitting-patches.html Sat Jun 7 09:41:03 2014 @@ -182,6 +182,34 @@ your fork and branch to compare the diff
  • Git at Apache
  • +

    Google's Patch Reward program

    + +

    During SFHTML5 Google announced that they adding the Apache Struts project to +the Google's Security Patch Reward Program.

    + +

    What does it mean?

    + +

    If you prepared a patch that eliminates a security vulnerability or improves existing security mechanism +you can get a bounty :-) You will find more details on +the Google's blog + or under the link above, just to give you a quick guideline how does it work:

    + +
      +
    • prepare a patch and submit it to our JIRA, +it can be a Pull Request on GitHub as well, but must reference the JIRA ticket.
    • +
    • let us know that you did something great, post a message to Struts Dev mailing list
    • +
    • we will review the patch and if it's a real great thing then we will merge it into our code base
    • +
    • just wait on official release of the Apache Struts and now you can request the reward from Google :-)
    • +
    + +

    NOTE

    + +

    If you are concerned that your patch can disclose a security vulnerability, instead of submitting it as a ticket, +send it directly to the Struts Security team. This will give us the possibility +to prepare a new release with your patch in secret.

    + +

    Have fun and code!

    +