Re: Security Permissions

Yes - if we want to do it at all. Ralph > On Sep 15, 2015, at 9:15 AM, Gary Gregory wrote: > > On Fri, Sep 11, 2015 at 4:41 PM, Gary Gregory > wrote: > Ah, so you are talking about doing this for all of Log4j, not just something > we are missing in log4j-jul? >

Re: Security Permissions

On Fri, Sep 11, 2015 at 4:41 PM, Gary Gregory wrote: > Ah, so you are talking about doing this for all of Log4j, not just > something we are missing in log4j-jul? > Ping. For 2.5? Gary > > Gary > > On Fri, Sep 11, 2015 at 4:32 PM, Ralph Goers > wrote: > >> j.u.l.LogManager checks LoggingPerm

Re: Security Permissions

Ah, so you are talking about doing this for all of Log4j, not just something we are missing in log4j-jul? Gary On Fri, Sep 11, 2015 at 4:32 PM, Ralph Goers wrote: > j.u.l.LogManager checks LoggingPermission(“control”) on > addPropertyChangeListener, removePropertyChangeListener, readConfigurati

Re: Security Permissions

j.u.l.LogManager checks LoggingPermission(“control”) on addPropertyChangeListener, removePropertyChangeListener, readConfiguration, reset, and checkAccess. j.u.l.Logger checks LoggingPermission(“control”) on setFilter, addHandler, removeHandler, setUseParentHandlers, and setParent. j.u.l.Memory

Re: Security Permissions

The last time I looked at that it looked like we were doing the right thing. But we might be talking about a different part of the code. Can you be more specific? Gary On Fri, Sep 11, 2015 at 1:55 PM, Ralph Goers wrote: > I was noticing the other day in the jul javadoc that operations that > m

Security Permissions

I was noticing the other day in the jul javadoc that operations that modify the configuration check the security manager for a LoggingPermission. Any thoughts on whether we should also be checking the same permissions? Ralph -