[wildfly-dev] my 2 cents on Security Manager discussion

[arjan tijms]

Hi,

Just wondering, but what is the primary use case for a security manager
server side?

While the model obviously makes sense for Applets and Webstart where
untrusted code is executed on the user's machine, I found it to be
extremely rare for a server to run untrusted code. In fact, I don't think
I've ever seen this situation.

There's maybe a case to prevent privilege escalation in case of a
legitimate app being hacked, but in practice it doesn't look like a
security manager is really being used a lot for that, is it? Instead the
default thing to do there seems to be to run the AS under a user with
limited rights on the host OS and/or use things like SELinix or Virtual
Servers (e.g. XEN) to isolate the complete AS.

Kind regards,
Arjan Tijms





On Sat, Apr 19, 2014 at 1:53 AM, Jason T. Greene <jgreene at redhat.com> wrote:

>
>
> Sent from my iPhone
>
> > On Apr 18, 2014, at 5:50 PM, Stuart Douglas <stuart.w.douglas at gmail.com>
> wrote:
> >
> >
> > Enabling the security manager by default is a terrible idea.
>
> +1000
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20140419/e8a491c6/attachment.html