[JBoss JIRA] (WFLY-3932) Enable security manager via JBoss Modules
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3932?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-3932:
-----------------------------------
Only the main modules (standalone, domain server, and domain host) need to import the dependency with services.
> Enable security manager via JBoss Modules
> -----------------------------------------
>
> Key: WFLY-3932
> URL: https://issues.jboss.org/browse/WFLY-3932
> Project: WildFly
> Issue Type: Feature Request
> Components: Security Manager
> Reporter: James Perkins
> Assignee: James Perkins
>
> In WildFly Core the security manager can be enabled via the {{-secmgr}} argument or setting the {{SECMGR=true}} environment variable. In order for this change to work correctly the {{WildFlySecurityManager.install()}} needs to be disabled.
> Also all modules that declare a dependency on {{org.wildfly.security.manager}} need to export the services.
> Tests need to be updated to use the {{-secmgr}} argument rather than {{-Djava.security.manager}}.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (ELY-43) Clean up Base64
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/ELY-43?page=com.atlassian.jira.plugin.sys... ]
Jason Greene commented on ELY-43:
---------------------------------
It's up to you guys if you want the code. (I would just copy the source for now if so). I more just wanted you to know it existed, and it had been already tested and tuned.
> Clean up Base64
> ---------------
>
> Key: ELY-43
> URL: https://issues.jboss.org/browse/ELY-43
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Utils
> Reporter: Darran Lofthouse
> Assignee: Farah Juma
> Fix For: 1.0.0.Beta1
>
>
> The Base64 implementation has been split out of PasswordUtils some additional steps are needed to finish cleaning it up: -
> - Look at switching to input and output streams instead of the custom iterators it is using.
> - Consider the ByteStringBuilder from SASL
> - As potentially more visible ensure clearer method names.
> - Ensure adequate javadoc and cross referencing of standards supported.
> e.g. If we implement an RFC ensure the number is referenced.
> - Testing of each variant
> - Consider optional support, e.g. decoding a padded String
> - Go beyond testing we can decode what we encode and ensure pre-encoded values can be handled adequately.
> Any other clean up here that seems relevant.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months