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

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2022/10/14 13:50:00 UTC

[jira] [Resolved] (KARAF-7423) Add logback configuration option

     [ https://issues.apache.org/jira/browse/KARAF-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved KARAF-7423.
-----------------------------------------
    Fix Version/s: 4.3.8
                   4.4.2
       Resolution: Fixed

> Add logback configuration option
> --------------------------------
>
>                 Key: KARAF-7423
>                 URL: https://issues.apache.org/jira/browse/KARAF-7423
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf
>            Reporter: Ian Thiemann
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 4.3.8, 4.4.2
>
>
> Since the log4j vulnerability of last year we've been having trouble using karaf logging in some systems that exclude vulnerable versions of log4j as a security policy. Even if log4j is not used as a logger, the configuration syntax of it is used, which requires including the log4j jar.
> We would like to have the option of using logback configuration as an added alternative to log4j, so that we can use the logging functionality on secure systems that exclude log4j.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)