10:27 a.m.
Hello Brian
Speaking for Weld codebase, I have already removed SM references for the
upcoming Weld 6 (EE 11, CDI 4.1) some time ago.
Here's the Weld issue - https://issues.redhat.com/browse/WELD-2789
And the PR - https://github.com/weld/core/pull/2983
I did that based on the fact that EE 11 states that it removes all use of
SM as one of its key changes (https://jakarta.ee/specifications/platform/11/
).
Plus, I am also aware of the WFLY issue that aimed to fail boot in EE 11 if
SM was detected - https://issues.redhat.com/browse/WFLY-19287
However, based on your email, it seems that this is a problem for WFLY but
I am failing to see why.
If EE 11 doesn't aim to support SM, why do we need to keep it in future
WFLY versions?
Regards
Matej
On Tue, Nov 19, 2024 at 4:27 PM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
tl;dr; Do not remove security manager calls from WildFly or its
components! Not unless you want and are able to maintain a branch
supporting them for many years.
I don't know all the details, but from a few discussions I've seen in the
last hour it seems that the promised removal of runtime support for the
Security Manager[1] has landed in an SE 24 update.
This change means in an SE 24 environment you can no longer enable the SM
and it will fail if you try. So this will certainly affect our code that's
meant to run on SE 24 and later; we'll need to adapt to not try and turn it
on.
What this *should not* mean is calls to SM-related APIs in SE will fail.
They should still work; they just don't do any enforcement. This isn't some
odd situation since for decades now the vast majority of calls to SM APIs
don't result in enforcement -- because the user doesn't enable the SM.
WildFly is going to support Java SE versions where the SM works for many
many more years. It's only in the upcoming WF 35 that we're dropping
support for SE 11. So who knows how much longer we'll need to support SE 21.
If you break SM support in a component, that stream will no longer be
usable in typical WF!
We'll need to do things to prepare for the day when SM APIs are removed
from SE and we shouldn't ignore that task. But please don't break things.
Kudos to those of you like Richard Opalka and James Perkins who are
keeping an eye on things and noticed this promptly.
[1] https://openjdk.org/jeps/486
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...