February 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8854) Cannot turn off HDScanner in AS6

by Chris Jansen (JIRA)

Cannot turn off HDScanner in AS6 -------------------------------- Key: JBAS-8854 URL: https://issues.jboss.org/browse/JBAS-8854 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.Final Environment: 64bit Linux, JDK1.6.0_23 Reporter: Chris Jansen Assignee: Ales Justin Disabling the HDscanner by following the doc http://community.jboss.org/wiki/turndeploymentscannerDown does not work. It appears that the profile service starts the HDScanner at boot - removing the entry <property name="hdScannerFactory"><inject bean="HDScannerFactory" /></property> from conf/bootstrap/profile.xml causes an NPE in BasicProfileServiceBootstrap.java: 2011-02-03 17:58:46,069 ERROR [ProfileServiceBootstrap] (Thread-2) failed to start server: java.lang.NullPointerException at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:141) [:6.0.0.Final] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final] at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
10
0 / 0

[JBoss JIRA] Created: (SECURITY-563) Exception javax.crypto.BadPaddingException: Given final block not properly padded thrown when decrypting

by Tom Ross (JIRA)

Exception javax.crypto.BadPaddingException: Given final block not properly padded thrown when decrypting --------------------------------------------------------------------------------------------------------- Key: SECURITY-563 URL: https://issues.jboss.org/browse/SECURITY-563 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: JBossSecurity_2.0.4.SP6 Environment: JBoss EAP 5.1 Reporter: Tom Ross Assignee: Anil Saldhana Exception "javax.crypto.BadPaddingException: Given final block not properly padded" is thrown when trying to decrypt a password like "dv". It looks like decrypt() method can not handle passwords that have been encrypted with "-" in front. "dv" is encrypted as -7f16992f0aa153. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
3
0 / 0

[JBoss JIRA] Created: (JBADMCON-160) Java Heap Size error during EAR deployment

by Hakan Junior (JIRA)

Java Heap Size error during EAR deployment ------------------------------------------ Key: JBADMCON-160 URL: https://issues.jboss.org/browse/JBADMCON-160 Project: JBoss Admin Console Issue Type: Bug Environment: JBoss AS 6.0.0.Final, Windows 7, Sun JDK 1.6.11 Reporter: Hakan Junior Priority: Critical Attachments: jboss.txt We are trying to deploy an EAR file which has size approx. 280MB. While deploying via admin-console, it throws Java Heap Size error and related stacktrace is attached to this issue. However, if we deploy via putting the file in server/standard/deploy folder no error occurs and everything goes well. Our Java_opts in run.conf.bat is set as; "JAVA_OPTS=-Xms512M -Xmx1024M -XX:MaxPermSize=512M" -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBADMCON-160) Java Heap Size error during EAR deployment

by Hakan Junior (JIRA)

[ https://issues.jboss.org/browse/JBADMCON-160?page=com.atlassian.jira.plug... ] Hakan Junior updated JBADMCON-160: ---------------------------------- Attachment: jboss.txt > Java Heap Size error during EAR deployment > ------------------------------------------ > > Key: JBADMCON-160 > URL: https://issues.jboss.org/browse/JBADMCON-160 > Project: JBoss Admin Console > Issue Type: Bug > Environment: JBoss AS 6.0.0.Final, Windows 7, Sun JDK 1.6.11 > Reporter: Hakan Junior > Priority: Critical > Labels: admin-console > Attachments: jboss.txt > > > We are trying to deploy an EAR file which has size approx. 280MB. While deploying via admin-console, it throws Java Heap Size error and related stacktrace is attached to this issue. However, if we deploy via putting the file in server/standard/deploy folder no error occurs and everything goes well. > Our Java_opts in run.conf.bat is set as; "JAVA_OPTS=-Xms512M -Xmx1024M -XX:MaxPermSize=512M" -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-344) Error decrypting datasource password with SecureIdentityLoginModule

by Marcus Moyses (JIRA)

Error decrypting datasource password with SecureIdentityLoginModule ------------------------------------------------------------------- Key: SECURITY-344 URL: https://jira.jboss.org/jira/browse/SECURITY-344 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2.SP3 Reporter: Marcus Moyses Assignee: Marcus Moyses Fix For: 2.0.2.SP5 During password decryption using SecureIdentityLoginModule there could be an error due to missing leading zeros for certain passwords. This error might appear in the log: [SecureIdentityLoginModule] Failed to decode password javax.crypto.IllegalBlockSizeException: Input length must be multiple of 8 when decrypting with padded cipher 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.jboss.resource.security.SecureIdentityLoginModule.decode(SecureIdentityLoginModule.java:173) at org.jboss.resource.security.SecureIdentityLoginModule.commit(SecureIdentityLoginModule.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
5
0 / 0

[JBoss JIRA] Created: (SECURITY-562) Release PicketBox 3.0.0.Final

by Anil Saldhana (JIRA)

Release PicketBox 3.0.0.Final ----------------------------- Key: SECURITY-562 URL: https://issues.jboss.org/browse/SECURITY-562 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Release Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-530) Implement a TOTP Login Module

by Anil Saldhana (JIRA)

Implement a TOTP Login Module ----------------------------- Key: SECURITY-530 URL: https://jira.jboss.org/browse/SECURITY-530 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_CR1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_CR2 It should be possible for an user to enter a TOTP value from any handheld device into a text box in the login form of a web application. This login module can then validate the totp entered. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-659) unable to download archetype-catalog.xml from releases repo

by Ian Springer (JIRA)

unable to download archetype-catalog.xml from releases repo ----------------------------------------------------------- Key: JBBUILD-659 URL: https://jira.jboss.org/browse/JBBUILD-659 Project: JBoss Build System Issue Type: Bug Components: Artifact Repositories Affects Versions: Maven Repository Nexus Rollout Reporter: Ian Springer $ wget https://repository.jboss.org/nexus/content/repositories/releases/archetyp... --2010-11-02 15:28:40-- https://repository.jboss.org/nexus/content/repositories/releases/archetyp... Resolving repository.jboss.org... 10.5.105.13 Connecting to repository.jboss.org|10.5.105.13|:443... connected. HTTP request sent, awaiting response... 500 Internal Server Error 2010-11-02 15:28:42 ERROR 500: Internal Server Error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4078) DeploymentManager.getAvailableModules() returns null

by Libor Kotouc (JIRA)

DeploymentManager.getAvailableModules() returns null ---------------------------------------------------- Key: JBAS-4078 URL: http://jira.jboss.com/jira/browse/JBAS-4078 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Environment: JBoss 5.0.0.beta2 trunk build 20070206, JDK 1.5.0_08 Reporter: Libor Kotouc Assigned To: Dimitris Andreadis Priority: Critical This issue blocks an integration of JBoss AS 5 into NetBeans IDE. Steps to reproduce the behavior: 1. create a simple web application and copy the .war file into the deploy directory (I used the 'default' server) 2. start JBoss server (./run.sh) 3. run the following code from a J2SE application (I added JBoss jars to the classpath): public class Main { public static void main(String[] args) { try { javax.enterprise.deploy.spi.factories.DeploymentFactory df = new org.jboss.deployment.spi.factories.DeploymentFactoryImpl(); javax.enterprise.deploy.spi.DeploymentManager dm; dm = df.getDeploymentManager("http://org.jboss.deployment/jsr88", null, null); javax.enterprise.deploy.spi.Target[] targets = dm.getTargets(); javax.enterprise.deploy.spi.TargetModuleID[] modules; modules = dm.getAvailableModules(javax.enterprise.deploy.shared.ModuleType.WAR, targets); System.out.println(targets.length + " " + targets[0]); System.out.println(modules); } catch (javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException ex) { } catch (javax.enterprise.deploy.spi.exceptions.TargetException ex) { } } } The output of System.out.println statements is: 1 org.jboss.deployment.spi.JMXTarget@161d36b null I expect the module representing the web application, but null is returned. -- 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

13 years, 12 months

4
5
0 / 0

[JBoss JIRA] Created: (JGRP-1279) ENCRYPT: algorithm provider only half implemented

by Bela Ban (JIRA)

ENCRYPT: algorithm provider only half implemented ------------------------------------------------- Key: JGRP-1279 URL: https://issues.jboss.org/browse/JGRP-1279 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.6.19, 2.12 [Dennis Reed] ENCRYPT allows the asym_provider to be specified. But it only uses it for the KeyGenerator lookup, not the Cipher lookup. And the sym_provider is hard-coded to null. Is there a reason the sym_provider isn't configurable, and that the providers aren't used for the Cipher lookups? This is causing issues for a customer, because they have an application that inserts a security provider at the beginning of the list. When JGroups first starts, it uses the default provider (BouncyCastle), but if there's a shun/reconnect after the application has inserted its provider, JGroups switches to the application's provider. And since some members are now using a different provider, they can't communicate. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2011