[
https://issues.apache.org/jira/browse/QPID-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752011#comment-17752011
]
ASF subversion and git services commented on QPID-8616:
-------------------------------------------------------
Commit 6334892a26e869a531b546ea6269395693c02d23 in qpid-broker-j's branch
refs/heads/main from Tomas Vavricka
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=6334892a26 ]
QPID-8616 Fixed Javadoc links
> [Broker-J] Privacy Violation: Heap Inspection in ManagedUser
> ------------------------------------------------------------
>
> Key: QPID-8616
> URL: https://issues.apache.org/jira/browse/QPID-8616
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Affects Versions: qpid-java-broker-9.0.0
> Reporter: Daniil Kirilyuk
> Priority: Minor
> Fix For: qpid-java-broker-9.0.1
>
>
> Sensitive data (such as passwords) stored in memory can be leaked if memory
> is not cleared after use. Often, Strings are used store sensitive data,
> however, since String objects are immutable, removing the value of a String
> from memory can only be done by the JVM garbage collector. The garbage
> collector is not required to run unless the JVM is low on memory, so there is
> no guarantee as to when garbage collection will take place. In the event of
> an application crash, a memory dump of the application might reveal sensitive
> data.
> Approach used in QPID-8583 should be applied to class ManagedUser.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
