JDK-6463832 : Incorrect java.security.debug help messages
  • Type: Bug
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-08-25
  • Updated: 2011-05-02
  • Resolved: 2011-05-02
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7 b03Fixed
Related Reports
Relates :  
JDK-6466247 - java.security.debug permission= and codebase= options do not work
Description
The java.security.debug help message shows that the "permission.<classname>" option will only dump debug output if the specified permission, and the "codebase.<URL>" option will only dump debug output if the specified codebase.

However, it seems that the options should be "permission=<classname>" and "codebase=<URL>". The "permission.<classname>" and "codebase.<URL>" deny to work.
Comments
EVALUATION Before bug 4945983, there are no explicit rules about the format of "java.security.debug" and "java.security.auth.debug". All debug options are searched by trying to find a case-insensetive sub-string from the "java.security.debug"/"java.security.auth.debug" definition. However, after the fix of 4945983, two rules are introduced implicit: 1. the "permission=<classname>" and "codebase=<URL>" should be separated from other options with a comma. 2. the "<classname>" and "<URL>" in the above options are case-sensitive. Two things should be addressed: 1. whether or not we should explicit define a multiple options separator. 2. The changes should be documented.
26-08-2006