[nanocontainer-scm] [jira] Updated: (NANO-105) Rebind in NanoNamingImpl leads to security exception in Server
jira-yCVjj/[email protected] Mon, 4 Oct 2004 11:43:51 -0400 (EDT)
| Newsgroups | gmane.comp.java.nanocontainer.cvs |
|---|---|
| Message-ID | <[email protected]> |
The following issue has been updated:
Updater: Philipp Meier (mailto:meier-cWh1PtA/[email protected])
Date: Mon, 4 Oct 2004 11:42 AM
Comment:
Path for the issue. Additionally adds a IllegalArgumentException be thrown by NanoNamingImpl if the componentKey cannot be found.
Changes:
Attachment changed to remoting-rebind-invalid.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/NANO-105?page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/NANO-105
Here is an overview of the issue:
---------------------------------------------------------------------
Key: NANO-105
Summary: Rebind in NanoNamingImpl leads to security exception in Server
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: NanoContainer
Components:
remoting
Assignee:
Reporter: Philipp Meier
Created: Mon, 4 Oct 2004 11:41 AM
Updated: Mon, 4 Oct 2004 11:42 AM
Description:
NanoNamingImpl rebinds the ComponentAdapters which leads to a SecurityException if the server resides on a different host than the client. This is due to a security restriction in RMI which forbinds calling bind if the method call was induced by a remote call.
The rebinding is IMHO unnessecary an can be omitted. I have attached a patch. There is no unit test for this issue because it's a functional test and I have no clue how to test this reasonably.
The pachted version is used in production by me and I found no side effects.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira