[JBoss JIRA] (WFLY-4576) JCE jar file inside a deployment fails the signature check
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-4576?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-4576:
-----------------------------------
The bug still needs to be fixed though, somehow. The VFS URL should be resolving to the JAR file, I suspect.
> JCE jar file inside a deployment fails the signature check
> ------------------------------------------------------------
>
> Key: WFLY-4576
> URL: https://issues.jboss.org/browse/WFLY-4576
> Project: WildFly
> Issue Type: Bug
> Components: VFS
> Affects Versions: 9.0.0.Beta2
> Environment: Wildfly build from master on April 22, 2015
> Reporter: Tom Fonteyne
> Assignee: Tomaz Cerar
> Attachments: bouncycastle.zip
>
>
> deploy a war file which contains the bouncycastle (or any other JCE) signed jar file. Initialise and try to use a cipher results in a failure due to VFS not being able to read and verify the file
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFLY-4576) JCE jar file inside a deployment fails the signature check
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/WFLY-4576?page=com.atlassian.jira.plugin.... ]
Tom Fonteyne commented on WFLY-4576:
------------------------------------
David came wit this workaround:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<resources>
<resource-root path="WEB-INF/lib/bcprov-jdk15on-1.51.jar" use-physical-code-source="true"/>
</resources>
</deployment>
</jboss-deployment-structure>
which work brilliant.
> JCE jar file inside a deployment fails the signature check
> ------------------------------------------------------------
>
> Key: WFLY-4576
> URL: https://issues.jboss.org/browse/WFLY-4576
> Project: WildFly
> Issue Type: Bug
> Components: VFS
> Affects Versions: 9.0.0.Beta2
> Environment: Wildfly build from master on April 22, 2015
> Reporter: Tom Fonteyne
> Assignee: Tomaz Cerar
> Attachments: bouncycastle.zip
>
>
> deploy a war file which contains the bouncycastle (or any other JCE) signed jar file. Initialise and try to use a cipher results in a failure due to VFS not being able to read and verify the file
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFLY-4576) JCE jar file inside a deployment fails the signature check
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/WFLY-4576?page=com.atlassian.jira.plugin.... ]
Tom Fonteyne edited comment on WFLY-4576 at 5/1/15 10:32 AM:
-------------------------------------------------------------
David came with this workaround:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<resources>
<resource-root path="WEB-INF/lib/bcprov-jdk15on-1.51.jar" use-physical-code-source="true"/>
</resources>
</deployment>
</jboss-deployment-structure>
which work brilliant.
was (Author: tfonteyn):
David came wit this workaround:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<resources>
<resource-root path="WEB-INF/lib/bcprov-jdk15on-1.51.jar" use-physical-code-source="true"/>
</resources>
</deployment>
</jboss-deployment-structure>
which work brilliant.
> JCE jar file inside a deployment fails the signature check
> ------------------------------------------------------------
>
> Key: WFLY-4576
> URL: https://issues.jboss.org/browse/WFLY-4576
> Project: WildFly
> Issue Type: Bug
> Components: VFS
> Affects Versions: 9.0.0.Beta2
> Environment: Wildfly build from master on April 22, 2015
> Reporter: Tom Fonteyne
> Assignee: Tomaz Cerar
> Attachments: bouncycastle.zip
>
>
> deploy a war file which contains the bouncycastle (or any other JCE) signed jar file. Initialise and try to use a cipher results in a failure due to VFS not being able to read and verify the file
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFLY-4576) JCE jar file inside a deployment fails the signature check
by Tom Fonteyne (JIRA)
Tom Fonteyne created WFLY-4576:
----------------------------------
Summary: JCE jar file inside a deployment fails the signature check
Key: WFLY-4576
URL: https://issues.jboss.org/browse/WFLY-4576
Project: WildFly
Issue Type: Bug
Components: VFS
Affects Versions: 9.0.0.Beta2
Environment: Wildfly build from master on April 22, 2015
Reporter: Tom Fonteyne
Assignee: Tomaz Cerar
deploy a war file which contains the bouncycastle (or any other JCE) signed jar file. Initialise and try to use a cipher results in a failure due to VFS not being able to read and verify the file
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFLY-1391) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861
by Tom Ross (JIRA)
[ https://issues.jboss.org/browse/WFLY-1391?page=com.atlassian.jira.plugin.... ]
Tom Ross closed WFLY-1391.
--------------------------
Resolution: Duplicate Issue
Fix in JBossTM code.
> ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-1391
> URL: https://issues.jboss.org/browse/WFLY-1391
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0.0.Alpha1
> Environment: JBoss EAP 6.1
> Reporter: Tom Ross
> Assignee: Jason Greene
>
> The expression value for node identifier is not being evaluated correctly. Setting it to:
> {noformat}
> /subsystem=transactions:write-attribute(name=node-identifier,value="${jboss.tx.node.id}")
> {noformat}
> where jboss.tx.node.id is supplied on command line as
> -Djboss.tx.node.id=111
> results in warning at start-up
> {noformat}
> 09:53:18,615 WARN [com.arjuna.ats.arjuna] (http-localhost/127.0.0.1:8080-1) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFLY-1391) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861
by Tom Ross (JIRA)
[ https://issues.jboss.org/browse/WFLY-1391?page=com.atlassian.jira.plugin.... ]
Tom Ross commented on WFLY-1391:
--------------------------------
Closing this issue since it has been fix in TM code.
> ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-1391
> URL: https://issues.jboss.org/browse/WFLY-1391
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0.0.Alpha1
> Environment: JBoss EAP 6.1
> Reporter: Tom Ross
> Assignee: Jason Greene
>
> The expression value for node identifier is not being evaluated correctly. Setting it to:
> {noformat}
> /subsystem=transactions:write-attribute(name=node-identifier,value="${jboss.tx.node.id}")
> {noformat}
> where jboss.tx.node.id is supplied on command line as
> -Djboss.tx.node.id=111
> results in warning at start-up
> {noformat}
> 09:53:18,615 WARN [com.arjuna.ats.arjuna] (http-localhost/127.0.0.1:8080-1) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFLY-1391) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861
by Tom Ross (JIRA)
[ https://issues.jboss.org/browse/WFLY-1391?page=com.atlassian.jira.plugin.... ]
Tom Ross commented on WFLY-1391:
--------------------------------
This is the fix for this issue.
> ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-1391
> URL: https://issues.jboss.org/browse/WFLY-1391
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.0.0.Alpha1
> Environment: JBoss EAP 6.1
> Reporter: Tom Ross
> Assignee: Jason Greene
>
> The expression value for node identifier is not being evaluated correctly. Setting it to:
> {noformat}
> /subsystem=transactions:write-attribute(name=node-identifier,value="${jboss.tx.node.id}")
> {noformat}
> where jboss.tx.node.id is supplied on command line as
> -Djboss.tx.node.id=111
> results in warning at start-up
> {noformat}
> 09:53:18,615 WARN [com.arjuna.ats.arjuna] (http-localhost/127.0.0.1:8080-1) ARJUNA012132: Supplied name of node contains reserved character -. Using Arjuna:-1162311861
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months