[Design of Security on JBoss] - JBNAME-8, updates to security in naming server
by scott.stark@jboss.org
https://jira.jboss.org/jira/browse/JBNAME-8
I have added security permission checks when running under a security manager to the jnpserver project for the 5.0.0.CR3 release. The following RuntimePermissions are required for sensitive NamingContext operations:
NamingContext.getHANamingServerForPartition requires RuntimePermission("org.jboss.naming.NamingContext.getHANamingServerForPartition");
NamingContext.setHANamingServerForPartition/removeHANamingServerForPartition requires RuntimePermission("org.jboss.naming.NamingContext.setHANamingServerForPartition");
NamingContext.getLocal requires RuntimePermission("org.jboss.naming.NamingContext.getLocal");
NamingContext.setLocal requires RuntimePermission("org.jboss.naming.NamingContext.setLocal");
The NamingServer has a new JndiPermission(String path, String actions) permission that is adopted from the OpenJDK java.io.FilePermission. It uses only the unix '/' path separator, and has the following actions:
bind - Context.bind permission
rebind - Context.rebind permission
unbind - Context.unbind permission.
lookup - Context.lookup permission.
list - Context.list permission.
listBindings - Context.listBindings permission.
createSubcontext - Context.createSubcontext permission
* - alias for all of the above actions
It also has a special path name <<ALL BINDINGS>> that matches any jndi path, similar to the FilePermission <<ALL FILES>> path.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180082#4180082
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180082
16 years, 5 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Message Scheduling
by ataylor
"clebert.suconic(a)jboss.com" wrote : "ataylor" wrote : A new packet will be created, say SessionScheduledSendMessage
|
| Can't we use just a Header Property on the message for that?
|
| on your clientProducer method:
|
| ....
| | message.setLongProperty("JBM-SCHEDULED-TIME", scheduledTime);
| | ...
|
Well we have a different send method completely so putting it on the message at send is redundant.
anonymous wrote : I wouldn't put this on PageMessage, as the StorageManager will have the same problem. Say... If you restart the server with a message scheduled to be delivered at 8:00 AM next morning, you need to reload that from the journal/database also.
We add a record to the journal separately that marks a message as scheduled.
anonymous wrote : I would or add a Property on the Message in such way it would be part of the encoding. Or a message Property, or a field being part of the encoding.anonymous wrote :
| |
| | We could do this, I don't think it makes much difference, we just have to make sure that the delivery time is saved.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180074#4180074
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180074
16 years, 5 months