[
https://issues.jboss.org/browse/AS7-5337?page=com.atlassian.jira.plugin.s...
]
Stefan Guilhen commented on AS7-5337:
-------------------------------------
I believe this is a duplicate of
https://issues.jboss.org/browse/AS7-5275. This bug has
nothing to do with PicketBox, its the result of a change in the vault session that is now
displaying the sharedkey by calling toString on a byte[].
In other words, 7.1 branch does new String(sharedKey) while master is now doing
sharedKey.toString(). Jeff's fix seems to do the trick but he closed the PR because a
test was failing and he believed it had something to do with the patch. I've tried to
patch locally and got clean testsuite runs, so I'll be opening a new PR.
Vault utility outputing incorrect shared key values
---------------------------------------------------
Key: AS7-5337
URL:
https://issues.jboss.org/browse/AS7-5337
Project: Application Server 7
Issue Type: Bug
Components: Security
Environment: No affects version as this is master as on 10th August 2012 - the
7.1 branch does not show this behaviour.
Reporter: Darran Lofthouse
Assignee: Stefan Guilhen
Fix For: 7.2.0.Alpha1
Adding a new vault entry results in the following (invalid) output - the shared key
appears to be an object reference: -
{code}
********************************************
Vault Block:darranl
Attribute Name:password
Shared Key:[B@79de256f
Configuration should be done as follows:
VAULT::darranl::password::[B@79de256f
********************************************
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira