[JBoss JIRA] (WFWIP-158) Artemis 2.7.0 logs password for STOMP protocol in clear text in debug logs
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFWIP-158?page=com.atlassian.jira.plugin.... ]
Miroslav Novak updated WFWIP-158:
---------------------------------
Steps to Reproduce:
Steps to reproduce:
{code}
git clone git@gitlab.mw.lab.eng.bos.redhat.com:jbossqe-eap/messaging-testsuite.git
cd messaging-testsuite/scripts/
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/703/artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=SslAuthenticationTestCase#testClusterWithSSL -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1553519968-ehsavoie-WFLY-11876-SNAPSHOT -DfailIfNoTests=false | tee log
{code}
> Artemis 2.7.0 logs password for STOMP protocol in clear text in debug logs
> --------------------------------------------------------------------------
>
> Key: WFWIP-158
> URL: https://issues.jboss.org/browse/WFWIP-158
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Justin Bertram
> Priority: Major
>
> If TRACE log is enabled for {{org.apache.activemq.artemis}} then StompProtoco is logging password in clear text:
> {code}
> 13:48:06,488 DEBUG [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) BeanUtils.populate(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, {needClientAuth=tru
> e, trustStorePassword=hornetqexample, keyStorePassword=hornetqexample, port=6445, sslEnabled=true, host=127.0.0.1, trustStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-weekly-common-ssl/eap-t
> estsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.truststore, keyStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-week
> ly-common-ssl/eap-testsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.keystore})
> ...
> 13:48:06,488 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, trustStorePassword, horn
> etqexample)
> ...
> 13:48:06,489 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, keyStorePassword, hornet
> qexample)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFWIP-158) Artemis 2.7.0 logs password for STOMP protocol in clear text in debug logs
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFWIP-158?page=com.atlassian.jira.plugin.... ]
Miroslav Novak commented on WFWIP-158:
--------------------------------------
[~jbertram] This issue popped when pre-testing Artemis 2.7.0 with Wildfly Master. Could you take a look, please?
> Artemis 2.7.0 logs password for STOMP protocol in clear text in debug logs
> --------------------------------------------------------------------------
>
> Key: WFWIP-158
> URL: https://issues.jboss.org/browse/WFWIP-158
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Justin Bertram
> Priority: Major
>
> If TRACE log is enabled for {{org.apache.activemq.artemis}} then StompProtoco is logging password in clear text:
> {code}
> 13:48:06,488 DEBUG [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) BeanUtils.populate(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, {needClientAuth=tru
> e, trustStorePassword=hornetqexample, keyStorePassword=hornetqexample, port=6445, sslEnabled=true, host=127.0.0.1, trustStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-weekly-common-ssl/eap-t
> estsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.truststore, keyStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-week
> ly-common-ssl/eap-testsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.keystore})
> ...
> 13:48:06,488 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, trustStorePassword, horn
> etqexample)
> ...
> 13:48:06,489 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, keyStorePassword, hornet
> qexample)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFWIP-158) Artemis 2.7.0 logs password for STOMP protocol in clear text in debug logs
by Miroslav Novak (Jira)
[ https://issues.jboss.org/browse/WFWIP-158?page=com.atlassian.jira.plugin.... ]
Miroslav Novak reassigned WFWIP-158:
------------------------------------
Assignee: Justin Bertram (was: Martyn Taylor)
> Artemis 2.7.0 logs password for STOMP protocol in clear text in debug logs
> --------------------------------------------------------------------------
>
> Key: WFWIP-158
> URL: https://issues.jboss.org/browse/WFWIP-158
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Justin Bertram
> Priority: Major
>
> If TRACE log is enabled for {{org.apache.activemq.artemis}} then StompProtoco is logging password in clear text:
> {code}
> 13:48:06,488 DEBUG [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) BeanUtils.populate(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, {needClientAuth=tru
> e, trustStorePassword=hornetqexample, keyStorePassword=hornetqexample, port=6445, sslEnabled=true, host=127.0.0.1, trustStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-weekly-common-ssl/eap-t
> estsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.truststore, keyStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-week
> ly-common-ssl/eap-testsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.keystore})
> ...
> 13:48:06,488 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, trustStorePassword, horn
> etqexample)
> ...
> 13:48:06,489 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, keyStorePassword, hornet
> qexample)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFWIP-158) Artemis 2.7.0 logs password for STOMP protocol in clear text in debug logs
by Miroslav Novak (Jira)
Miroslav Novak created WFWIP-158:
------------------------------------
Summary: Artemis 2.7.0 logs password for STOMP protocol in clear text in debug logs
Key: WFWIP-158
URL: https://issues.jboss.org/browse/WFWIP-158
Project: WildFly WIP
Issue Type: Bug
Components: Artemis
Reporter: Miroslav Novak
Assignee: Martyn Taylor
If TRACE log is enabled for {{org.apache.activemq.artemis}} then StompProtoco is logging password in clear text:
{code}
13:48:06,488 DEBUG [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) BeanUtils.populate(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, {needClientAuth=tru
e, trustStorePassword=hornetqexample, keyStorePassword=hornetqexample, port=6445, sslEnabled=true, host=127.0.0.1, trustStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-weekly-common-ssl/eap-t
estsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.truststore, keyStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-week
ly-common-ssl/eap-testsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.keystore})
...
13:48:06,488 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, trustStorePassword, horn
etqexample)
...
13:48:06,489 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService Thread Pool -- 86) setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516, keyStorePassword, hornet
qexample)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFWIP-157) Wildfly 16 incorrect working log zip rotator
by Игорь Дмитриев (Jira)
[ https://issues.jboss.org/browse/WFWIP-157?page=com.atlassian.jira.plugin.... ]
Игорь Дмитриев updated WFWIP-157:
---------------------------------
Description:
My logging profile configuration is:
1)
{code:xml}
<periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="true"/>
</periodic-size-rotating-file-handler>
{code}
File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size.
2)
{code:xml}
<periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="false"/>
</periodic-size-rotating-file-handler>
{code}
All work as expected, except each time corp.log reach 300k, appear pair .zip files with same content?
was:
My logging profile configuration is:
1)
{code:xml}
<periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="true"/>
</periodic-size-rotating-file-handler>
{code}
File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size.
2)
{code:xml}
<periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="false"/>
</periodic-size-rotating-file-handler>
{code}
All work as expected, except each time corp.log reach 300k, appear certain TWO SAME .zip files ?
> Wildfly 16 incorrect working log zip rotator
> --------------------------------------------
>
> Key: WFWIP-157
> URL: https://issues.jboss.org/browse/WFWIP-157
> Project: WildFly WIP
> Issue Type: Bug
> Components: Logging
> Reporter: Игорь Дмитриев
> Assignee: James Perkins
> Priority: Major
>
> My logging profile configuration is:
> 1)
> {code:xml}
> <periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true">
> <level name="ALL"/>
> <file relative-to="jboss.server.log.dir" path="corp.log"/>
> <rotate-size value="300k"/>
> <max-backup-index value="10000"/>
> <suffix value=".yyyy-MM-dd.zip"/>
> <append value="true"/>
> </periodic-size-rotating-file-handler>
> {code}
> File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size.
> 2)
> {code:xml}
> <periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true">
> <level name="ALL"/>
> <file relative-to="jboss.server.log.dir" path="corp.log"/>
> <rotate-size value="300k"/>
> <max-backup-index value="10000"/>
> <suffix value=".yyyy-MM-dd.zip"/>
> <append value="false"/>
> </periodic-size-rotating-file-handler>
> {code}
> All work as expected, except each time corp.log reach 300k, appear pair .zip files with same content?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFWIP-157) Wildfly 16 incorrect working log zip rotator
by Игорь Дмитриев (Jira)
[ https://issues.jboss.org/browse/WFWIP-157?page=com.atlassian.jira.plugin.... ]
Игорь Дмитриев updated WFWIP-157:
---------------------------------
Description:
My logging profile configuration is:
1)
{code:xml}
<periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="true"/>
</periodic-size-rotating-file-handler>
{code}
File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size.
2)
{code:xml}
<periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="false"/>
</periodic-size-rotating-file-handler>
{code}
All work as expected, except each time corp.log reach 300k, appear certain TWO SAME .zip files ?
was:
My logging profile configuration is:
1)
{code:xml}
<periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="true"/>
</periodic-size-rotating-file-handler>
{code:xml}
File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size.
2)
{code:xml}
<periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="false"/>
</periodic-size-rotating-file-handler>
{code:xml}
All work as expected, except each time corp.log reach 300k, appear certain TWO SAME .zip files ?
> Wildfly 16 incorrect working log zip rotator
> --------------------------------------------
>
> Key: WFWIP-157
> URL: https://issues.jboss.org/browse/WFWIP-157
> Project: WildFly WIP
> Issue Type: Bug
> Components: Logging
> Reporter: Игорь Дмитриев
> Assignee: James Perkins
> Priority: Major
>
> My logging profile configuration is:
> 1)
> {code:xml}
> <periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true">
> <level name="ALL"/>
> <file relative-to="jboss.server.log.dir" path="corp.log"/>
> <rotate-size value="300k"/>
> <max-backup-index value="10000"/>
> <suffix value=".yyyy-MM-dd.zip"/>
> <append value="true"/>
> </periodic-size-rotating-file-handler>
> {code}
> File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size.
> 2)
> {code:xml}
> <periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true">
> <level name="ALL"/>
> <file relative-to="jboss.server.log.dir" path="corp.log"/>
> <rotate-size value="300k"/>
> <max-backup-index value="10000"/>
> <suffix value=".yyyy-MM-dd.zip"/>
> <append value="false"/>
> </periodic-size-rotating-file-handler>
> {code}
> All work as expected, except each time corp.log reach 300k, appear certain TWO SAME .zip files ?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFWIP-157) Wildfly 16 incorrect working log zip rotator
by Игорь Дмитриев (Jira)
Игорь Дмитриев created WFWIP-157:
------------------------------------
Summary: Wildfly 16 incorrect working log zip rotator
Key: WFWIP-157
URL: https://issues.jboss.org/browse/WFWIP-157
Project: WildFly WIP
Issue Type: Bug
Components: Logging
Reporter: Игорь Дмитриев
Assignee: James Perkins
My logging profile configuration is:
1)
{code:xml}
<periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="true"/>
</periodic-size-rotating-file-handler>
{code:xml}
File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size.
2)
{code:xml}
<periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="false"/>
</periodic-size-rotating-file-handler>
{code:xml}
All work as expected, except each time corp.log reach 300k, appear certain TWO SAME .zip files ?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month