[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-1180) Formally reject hostnames which don't conform to RFC-952

Justin Bertram (JIRA) jira-events at lists.jboss.org
Fri Jan 15 21:44:53 EST 2010


     [ https://jira.jboss.org/jira/browse/JBREM-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram updated JBREM-1180:
----------------------------------

    Description: 
Host names which don't conform to RFC-952 [1] should be formally rejected.  This will save time diagnosing problems as org.jboss.remoting.InvokerLocator(String uri) does not handle non-conformant names properly and seemingly unrelated errors can occur as a result.  For example:

  InvokerLocator locator = new InvokerLocator("bisocket://UNDER_SCORE:4457//?JBM_clientMaxPoolSize=200");
  System.out.println(locator);
  locator = new InvokerLocator("bisocket://UNDERSCORE:4457/?JBM_clientMaxPoolSize=200");
  System.out.println(locator);

Results in:

  InvokerLocator [bisocket://192.168.2.2//?JBM_clientMaxPoolSize=200]
  InvokerLocator [bisocket://UNDERSCORE:4457/?JBM_clientMaxPoolSize=200]

The "_" breaks the parsing logic.



[1] http://www.ietf.org/rfc/rfc952.txt

  was:
Host names which don't conform to RFC-952 [1] should be formally rejected.  This will save time diagnosing problems as org.jboss.remoting.InvokerLocator(String uri) does not handle non-conformant names properly and seemingly unrelated errors can occur as a result.



[1] http://www.ietf.org/rfc/rfc952.txt



> Formally reject hostnames which don't conform to RFC-952
> --------------------------------------------------------
>
>                 Key: JBREM-1180
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1180
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.3.SP1
>            Reporter: Justin Bertram
>            Assignee: Ron Sigal
>
> Host names which don't conform to RFC-952 [1] should be formally rejected.  This will save time diagnosing problems as org.jboss.remoting.InvokerLocator(String uri) does not handle non-conformant names properly and seemingly unrelated errors can occur as a result.  For example:
>   InvokerLocator locator = new InvokerLocator("bisocket://UNDER_SCORE:4457//?JBM_clientMaxPoolSize=200");
>   System.out.println(locator);
>   locator = new InvokerLocator("bisocket://UNDERSCORE:4457/?JBM_clientMaxPoolSize=200");
>   System.out.println(locator);
> Results in:
>   InvokerLocator [bisocket://192.168.2.2//?JBM_clientMaxPoolSize=200]
>   InvokerLocator [bisocket://UNDERSCORE:4457/?JBM_clientMaxPoolSize=200]
> The "_" breaks the parsing logic.
> [1] http://www.ietf.org/rfc/rfc952.txt

-- 
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

        


More information about the jboss-remoting-issues mailing list