[jira] [Created] (STORM-3814) log4j

Franco Luong created STORM-3814: --- Summary: log4j Key: STORM-3814 URL: https://issues.apache.org/jira/browse/STORM-3814 Project: Apache Storm Issue Type: Bug Reporter: Franco Luong

[jira] [Closed] (STORM-3814) storm-core: Remediate log4j critical vulnerabilities -> 2.16.0 or newer, prefer 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franco Luong closed STORM-3814. --- > storm-core: Remediate log4j critical vulnerabilities -> 2.16.0 or newer, > prefer 2.17.1 >

[jira] [Updated] (STORM-3814) log4j

[ https://issues.apache.org/jira/browse/STORM-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franco Luong updated STORM-3814: Component/s: storm-core Affects Version/s: 1.2.3 2.3.0

[jira] [Commented] (STORM-3808) Bump log4j version to 2.16.0 (original ticket was 2.15.0)

[ https://issues.apache.org/jira/browse/STORM-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468085#comment-17468085 ] Franco Luong commented on STORM-3808: - This should be closed in favor of

[jira] [Updated] (STORM-3814) log4j

[ https://issues.apache.org/jira/browse/STORM-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franco Luong updated STORM-3814: Description: * [https://logging.apache.org/log4j/2.x/security.html]   *In order to remediate

[jira] [Updated] (STORM-3814) storm-core: Remediate log4j critical vulnerabilities -> 2.16.0 or newer, prefer 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franco Luong updated STORM-3814: Summary: storm-core: Remediate log4j critical vulnerabilities -> 2.16.0 or newer, prefer 2.17.1

[jira] [Updated] (STORM-3814) storm-core: Remediate log4j critical vulnerabilities -> 2.16.0 or newer, prefer 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franco Luong updated STORM-3814: Description: * [https://logging.apache.org/log4j/2.x/security.html]   *In order to remediate

[jira] [Commented] (STORM-3808) Bump log4j version to 2.16.0 (original ticket was 2.15.0)

[ https://issues.apache.org/jira/browse/STORM-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468068#comment-17468068 ] Franco Luong commented on STORM-3808: - Why is this listed as an "Improvement"?  That seems completely

[jira] [Updated] (STORM-3814) log4j

[ https://issues.apache.org/jira/browse/STORM-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franco Luong updated STORM-3814: Priority: Critical (was: Major) > log4j > - > > Key: STORM-3814 >

[jira] [Resolved] (STORM-3814) storm-core: Remediate log4j critical vulnerabilities -> 2.16.0 or newer, prefer 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franco Luong resolved STORM-3814. - Resolution: Duplicate > storm-core: Remediate log4j critical vulnerabilities -> 2.16.0 or newer,

[jira] [Commented] (STORM-3814) storm-core: Remediate log4j critical vulnerabilities -> 2.16.0 or newer, prefer 2.17.1

[ https://issues.apache.org/jira/browse/STORM-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468083#comment-17468083 ] Franco Luong commented on STORM-3814: - seems to be addressed by

[jira] [Created] (STORM-3815) allow option to disable sending of __send-iconnection metrics

Aaron Gresch created STORM-3815: --- Summary: allow option to disable sending of __send-iconnection metrics Key: STORM-3815 URL: https://issues.apache.org/jira/browse/STORM-3815 Project: Apache Storm