[JBoss JIRA] (WFCORE-135) Eliminate customized usage of RuntimePermission
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-135?page=com.atlassian.jira.plugin... ]
David Lloyd updated WFCORE-135:
-------------------------------
Description:
The JDK defines the entire domain of valid RuntimePermission names.
Here's a listing:
{noformat}
org.jboss.as.controller.AccessAuditContext#GET_ACCESS_AUDIT_CONTEXT
org.jboss.as.controller.ModelController#ACCESS_PERMISSION
org.jboss.as.controller.access.Caller#CREATE_CALLER_PERMISSION
org.jboss.as.controller.access.Caller#GET_SUBJECT_PERMISSION
org.jboss.as.controller.registry.ImmutableManagementResourceRegistration#ACCESS_PERMISSION
org.jboss.as.server.CurrentServiceContainer#LOOKUP_CURRENT_SERVICE_CONTAINER
org.jboss.as.server.CurrentServiceContainer#SET_CURRENT_SERVICE_CONTAINER
org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex#DEPLOYMENT_REFLECTION_INDEX_PERMISSION
org.jboss.as.server.deployment.service.SecuredServiceRegistry#PERMISSION
{noformat}
was:
The JDK defines the entire domain of valid RuntimePermission names.
Here's a listing:
{noformat}
org.jboss.as.naming.NamingContext#SET_ACTIVE_NAMING_STORE
org.jboss.as.security.remoting.RemotingContext#SET_CONNECTION_PERMISSION
org.jboss.as.security.remoting.RemotingContext#CLEAR_CONNECTION_PERMISSION
org.jboss.as.security.remoting.RemotingContext#GET_CONNECTION_PERMISSION
org.jboss.as.security.remoting.RemotingContext#IS_SET_PERMISSION
{noformat}
> Eliminate customized usage of RuntimePermission
> -----------------------------------------------
>
> Key: WFCORE-135
> URL: https://issues.jboss.org/browse/WFCORE-135
> Project: WildFly Core
> Issue Type: Task
> Components: Server
> Reporter: David Lloyd
> Assignee: Eduardo Martins
> Fix For: 1.0.0.CR1
>
>
> The JDK defines the entire domain of valid RuntimePermission names.
> Here's a listing:
> {noformat}
> org.jboss.as.controller.AccessAuditContext#GET_ACCESS_AUDIT_CONTEXT
> org.jboss.as.controller.ModelController#ACCESS_PERMISSION
> org.jboss.as.controller.access.Caller#CREATE_CALLER_PERMISSION
> org.jboss.as.controller.access.Caller#GET_SUBJECT_PERMISSION
> org.jboss.as.controller.registry.ImmutableManagementResourceRegistration#ACCESS_PERMISSION
> org.jboss.as.server.CurrentServiceContainer#LOOKUP_CURRENT_SERVICE_CONTAINER
> org.jboss.as.server.CurrentServiceContainer#SET_CURRENT_SERVICE_CONTAINER
> org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex#DEPLOYMENT_REFLECTION_INDEX_PERMISSION
> org.jboss.as.server.deployment.service.SecuredServiceRegistry#PERMISSION
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 5 months
[JBoss JIRA] (WFCORE-135) Eliminate customized usage of RuntimePermission
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-135?page=com.atlassian.jira.plugin... ]
David Lloyd moved WFLY-3917 to WFCORE-135:
------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-135 (was: WFLY-3917)
Component/s: Server
(was: Naming)
(was: Security)
Fix Version/s: 1.0.0.CR1
(was: 9.0.0.CR1)
> Eliminate customized usage of RuntimePermission
> -----------------------------------------------
>
> Key: WFCORE-135
> URL: https://issues.jboss.org/browse/WFCORE-135
> Project: WildFly Core
> Issue Type: Task
> Components: Server
> Reporter: David Lloyd
> Assignee: Eduardo Martins
> Fix For: 1.0.0.CR1
>
>
> The JDK defines the entire domain of valid RuntimePermission names.
> Here's a listing:
> {noformat}
> org.jboss.as.naming.NamingContext#SET_ACTIVE_NAMING_STORE
> org.jboss.as.security.remoting.RemotingContext#SET_CONNECTION_PERMISSION
> org.jboss.as.security.remoting.RemotingContext#CLEAR_CONNECTION_PERMISSION
> org.jboss.as.security.remoting.RemotingContext#GET_CONNECTION_PERMISSION
> org.jboss.as.security.remoting.RemotingContext#IS_SET_PERMISSION
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 5 months
[JBoss JIRA] (WFLY-3917) Eliminate customized usage of RuntimePermission
by David Lloyd (JIRA)
David Lloyd created WFLY-3917:
---------------------------------
Summary: Eliminate customized usage of RuntimePermission
Key: WFLY-3917
URL: https://issues.jboss.org/browse/WFLY-3917
Project: WildFly
Issue Type: Task
Components: Naming, Security
Reporter: David Lloyd
Assignee: Eduardo Martins
Fix For: 9.0.0.CR1
The JDK defines the entire domain of valid RuntimePermission names.
Here's a listing:
{noformat}
org.jboss.as.naming.NamingContext#SET_ACTIVE_NAMING_STORE
org.jboss.as.security.remoting.RemotingContext#SET_CONNECTION_PERMISSION
org.jboss.as.security.remoting.RemotingContext#CLEAR_CONNECTION_PERMISSION
org.jboss.as.security.remoting.RemotingContext#GET_CONNECTION_PERMISSION
org.jboss.as.security.remoting.RemotingContext#IS_SET_PERMISSION
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 5 months
[JBoss JIRA] (WFLY-3916) Eliminate customized usage of RuntimePermission
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3916?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-3916:
------------------------------
Component/s: Security
> Eliminate customized usage of RuntimePermission
> -----------------------------------------------
>
> Key: WFLY-3916
> URL: https://issues.jboss.org/browse/WFLY-3916
> Project: WildFly
> Issue Type: Task
> Components: Naming, Security
> Reporter: David Lloyd
> Assignee: Eduardo Martins
> Fix For: 9.0.0.CR1
>
>
> The JDK defines the entire domain of valid RuntimePermission names.
> Here's a listing:
> {noformat}
> org.jboss.as.naming.NamingContext#SET_ACTIVE_NAMING_STORE
> org.jboss.as.security.remoting.RemotingContext#SET_CONNECTION_PERMISSION
> org.jboss.as.security.remoting.RemotingContext#CLEAR_CONNECTION_PERMISSION
> org.jboss.as.security.remoting.RemotingContext#GET_CONNECTION_PERMISSION
> org.jboss.as.security.remoting.RemotingContext#IS_SET_PERMISSION
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 5 months
[JBoss JIRA] (WFLY-3916) Eliminate customized usage of RuntimePermission
by David Lloyd (JIRA)
David Lloyd created WFLY-3916:
---------------------------------
Summary: Eliminate customized usage of RuntimePermission
Key: WFLY-3916
URL: https://issues.jboss.org/browse/WFLY-3916
Project: WildFly
Issue Type: Task
Components: Naming
Reporter: David Lloyd
Assignee: Eduardo Martins
Fix For: 9.0.0.CR1
The JDK defines the entire domain of valid RuntimePermission names.
Here's a listing:
{noformat}
org.jboss.as.naming.NamingContext#SET_ACTIVE_NAMING_STORE
org.jboss.as.security.remoting.RemotingContext#SET_CONNECTION_PERMISSION
org.jboss.as.security.remoting.RemotingContext#CLEAR_CONNECTION_PERMISSION
org.jboss.as.security.remoting.RemotingContext#GET_CONNECTION_PERMISSION
org.jboss.as.security.remoting.RemotingContext#IS_SET_PERMISSION
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 5 months
[JBoss JIRA] (WFCORE-134) Make sure CLIWrapper doesn't use default encoding
by Emmanuel Hugonnet (JIRA)
Emmanuel Hugonnet created WFCORE-134:
----------------------------------------
Summary: Make sure CLIWrapper doesn't use default encoding
Key: WFCORE-134
URL: https://issues.jboss.org/browse/WFCORE-134
Project: WildFly Core
Issue Type: Bug
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Priority: Minor
CLIWrapper is using the default encoding which might lead to issue with non US locales.
Also take advantage of this fix to remove some hard coded strings from tests.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 5 months