This is an automated email from the ASF dual-hosted git repository.
kusal pushed a change to branch WW-5364-populate-allowlist
in repository https://gitbox.apache.org/repos/asf/struts.git
omit d431531c7 WW-5364 Enable allowlist for showcase
omit dbb75d77e WW-5364 Inject ProviderAllowlist into SecurityMemberAccess
omit 78e4cb617 WW-5364 Implement provider allowlist
add 198812fe8 WW-5364 Implement provider allowlist
add 3bf3e5f8d WW-5364 Inject ProviderAllowlist into SecurityMemberAccess
add ee442db9e WW-5364 Enable allowlist for showcase
add cf178dd14 WW-5364 Add Struts components to allowlist
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d431531c7)
\
N -- N -- N refs/heads/WW-5364-populate-allowlist (cf178dd14)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
apps/showcase/src/main/resources/struts.xml | 6 +++
.../providers/XmlDocConfigurationProvider.java | 10 ++--
.../xwork2/ognl/SecurityMemberAccess.java | 62 ++++++++++++++++++++++
.../src/main/resources/struts-excluded-classes.xml | 12 +++--
4 files changed, 80 insertions(+), 10 deletions(-)
