You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by GitBox <gi...@apache.org> on 2022/08/22 14:48:41 UTC

[GitHub] [logging-log4j2] jamezp commented on pull request #1006: LOG4J2-3579 Add privileged execution for ServiceLoading

jamezp commented on PR #1006:
URL: https://github.com/apache/logging-log4j2/pull/1006#issuecomment-1222467901

   I'm a +1 for the second (#1007) approach compared to this. It is more of a pain to ensure it's always used in a privileged action, but it's definitely more secure. There may be cases where an implementation or user might *not* want it privileged.
   
   WRT the `SecurityManager` as a whole. Yes it's deprecated in Java 17 and proposed for removal. However, there are some users that are required to use a `SecurityManager` for compliance reasons.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org