[JBoss JIRA] Created: (JGRP-604) ENCRYPT: issues with keystore
by Bela Ban (JIRA)
ENCRYPT: issues with keystore
-----------------------------
Key: JGRP-604
URL: http://jira.jboss.com/jira/browse/JGRP-604
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.7
Attachments: tmp2.xml
If we use ENCRYPT with a keystore and fragmentation, then ENCRYPT throws the following exception:
09:35:45,920 [WARN] [Incoming,demo,192.168.2.3:49952] ENCRYPT.up(): exception occurred decrypting message
javax.crypto.BadPaddingException: Given final block not properly padded
at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
at com.sun.crypto.provider.BlowfishCipher.engineDoFinal(DashoA12275)
at javax.crypto.Cipher.doFinal(DashoA12275)
at org.jgroups.protocols.ENCRYPT._decrypt(ENCRYPT.java:837)
at org.jgroups.protocols.ENCRYPT.decryptMessage(ENCRYPT.java:830)
at org.jgroups.protocols.ENCRYPT.handleUpMessage(ENCRYPT.java:673)
at org.jgroups.protocols.ENCRYPT.up(ENCRYPT.java:533)
at org.jgroups.protocols.UNICAST.handleDataReceived(UNICAST.java:573)
at org.jgroups.protocols.UNICAST.up(UNICAST.java:247)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:704)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)
at org.jgroups.protocols.FD.up(FD.java:322)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:309)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
at org.jgroups.protocols.Discovery.up(Discovery.java:250)
at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1512)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1456)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:613)
To reproduce:
- Create a configuration with the following entries present:
<ENCRYPT key_store_name="defaultStore.keystore" store_password="changeit" alias="myKey"/>
<FRAG2 frag_size="60000"/>
- Run RpcDispatcherTest.testLargeReturnValue (the stack has to include ENCRYPT and FRAG2).
Note that this error does not occur with
<ENCRYPT encrypt_entire_message="false" sym_init="128" sym_algorithm="AES/ECB/PKCS5Padding" asym_init="512" asym_algorithm="RSA"/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months
[JBoss JIRA] Created: (JBRULES-1358) DSL mapping not available in BRMS
by Ravi Shankar (JIRA)
DSL mapping not available in BRMS
---------------------------------
Key: JBRULES-1358
URL: http://jira.jboss.com/jira/browse/JBRULES-1358
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.0.3
Reporter: Ravi Shankar
Hi,
In the BRMS I did not find conversation of DSL to actual valid DRL syntax. For example in the eclipse plugin I created the following as in when clause:
Shopping Basket price is more than or equal to {value}
and in the mapping I put the following java code:
originalBasket : ShoppingBasket(descriptor == "originalBasket", cartTotal.value >= {value}) bestDiscounted : ShoppingBasket(descriptor == "bestDiscounted") currentDiscounted : ShoppingBasket(descriptor == "currentDiscounted")
so that when converting a .dslr into a .drl the conversion happens from business user's friendly version to developer friendly code. But I do not find a place in BRMS to specify such mappings.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months
[JBoss JIRA] Created: (JBRULES-1276) Drools toolbar should not appear in all perspectives and should reuse the standard "new" dropdown
by Willian Mitsuda (JIRA)
Drools toolbar should not appear in all perspectives and should reuse the standard "new" dropdown
-------------------------------------------------------------------------------------------------
Key: JBRULES-1276
URL: http://jira.jboss.com/jira/browse/JBRULES-1276
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Affects Versions: 4.0.2
Reporter: Willian Mitsuda
Assigned To: Mark Proctor
I just installed the drools plugin and noted that it automatically enables a drools toolbar in every perspective.
This is not a good UI policy because it looks like the plugin is trying to appear more important than the others. I have other plugins installed, and I don't like the drools button appearing by default in the C++ or the Profilling perspective, for example. It could be enabled by default just in the Drools perspective, since it exists, and the user could enable it on the others, if he desires.
Also, since your actions are all about resource creation, you could hook them into the standard "new" dropdown, instead of creating your own actionset. This should make your plugin to appear more integrated to Eclipse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 11 months