cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From exabrial <>
Subject [GitHub] cxf pull request #279: [WIP] Backport several CVE fixes to the 2.6.x Branch
Date Wed, 07 Jun 2017 20:15:21 GMT
GitHub user exabrial opened a pull request:

    [WIP] Backport several CVE fixes to the 2.6.x Branch

    [WIP] = Work in Progress, don't merge yet please
    Backporting several fixes to the 2.6.x branch.

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

    $ git pull cxf-outbound

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

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

    This closes #279
commit ac2842b8682e386882f04f56bbea13b00ba34098
Author: Romain manni-Bucau <>
Date:   2016-05-11T11:19:16Z

    2.6.x branch

commit 1a01c8bcdd9b9b038487c8cc7f692d65cfdfe39a
Author: Romain manni-Bucau <>
Date:   2016-05-11T16:09:21Z

    fixing CVE-2014-3577 + upgrading wss4j + ignoring invalid tests or instable ones (perf)

commit 2fef247abfaa315c5b806c2606ed36ff47abff11
Author: Jonathan S. Fisher <>
Date:   2017-06-07T20:08:05Z

    set to SNAPSHOT for development

commit 6caf7910f741317a6eabd1b7ccee0d9345f654d3
Author: Tod Bookless <>
Date:   2017-06-01T16:33:30Z

    Merge pull request #2 from exabrial/Add-toolchain-support
    Add toolchain support to CXF to support builds on TT infra

commit 73963a760286eeacc425f4cd366b7dd8dbf20795
Author: Tod Bookless <>
Date:   2017-06-01T17:26:13Z

    Merge pull request #1 from exabrial/TRIBESTRM_3972_CVE_2016_8739
    [Tribestrm-3972] cve-2016-8739

commit d8e4ea6a67b4093f703387919a98f0026a9d6724
Author: Tod Bookless <>
Date:   2017-06-02T22:48:04Z

    Merge pull request #3 from exabrial/TRIBESTRM-3973_CVE-2016-6812
    [TRIBESTRM-3973] CVE-2016-6812


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 or file a JIRA ticket
with INFRA.

View raw message