https://bugzilla.redhat.com/show_bug.cgi?id=1342219
Coty Sutherland <csutherl(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |NOTABUG
Last Closed| |2016-09-25 16:30:07
--- Comment #12 from Coty Sutherland <csutherl(a)redhat.com> ---
I updated the package and tested but the issue is still reproducible.
Thanks for testing.
So, the recommendation is to me let upstream know about this issue,
right?
Yes, but this looks like expected behavior to me. All applications should not
have access to the specified environment variable, so if your application needs
it, then you need to adjust the policy accordingly.
sorry, i missed something: did the test case work for you?
No, I tested with ASF tomcat 8.0.32 and 8.0.35 and both show the same behavior
when using the security manager. The problem is that the default policy does
not allow this behavior and therefore it's expected.
If you don't agree with that assessment please open an upstream bug with ASF
tomcat and suggest a change in the policy to be less strict.
--
You are receiving this mail because:
You are on the CC list for the bug.