[ 
https://issues.apache.org/jira/browse/DERBY-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John H. Embretsen updated DERBY-3322:
-------------------------------------

    Attachment: tadminnetservcustom.html
                d3322v01.diff

Attached a patch d3322v01.diff which fixes this issue. The patch touches the 
following file:

M      src/adminguide/tadminnetservcustom.dita

The patch removes references to the non-existing property derby.security.host, 
and also fixes a couple of typos and omissions.

Also attached the resulting html output (tadminnetservcustom.html) for review 
purposes.

Please review/commit. This fix is suitable for both trunk and the 10.3 branch.

> Server guide refers to phantom property in template policy file for the 
> Network Server
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-3322
>                 URL: https://issues.apache.org/jira/browse/DERBY-3322
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.3.1.4, 10.3.2.1
>         Environment: N/A
>            Reporter: John H. Embretsen
>            Assignee: John H. Embretsen
>            Priority: Trivial
>             Fix For: 10.4.0.0
>
>         Attachments: d3322v01.diff, tadminnetservcustom.html
>
>
> The Server and Administration guide contains a section about customizing the 
> Network Server's security policy, based on the template policy:
> http://db.apache.org/derby/docs/dev/adminguide/tadminnetservcustom.html
> This section mentions that the variable ${derby.security.host} should be 
> replaced with a suitable value.
>  
> However, the template policy, at /demo/templates/server.policy (released 
> binaries) or java/drda/org/apache/derby/drda/template.policy (SVN codeline), 
> does not refer to any variable or property called ${derby.security.host}. 
> Instead, the policy file specifies the wildcard address, with appropriate 
> comments:
> <quote>
> // Accept connections from any host. Derby is listening to the host
> // interface specified via the -h option to "NetworkServerControl
> // start" on the command line, via the address parameter to the
> // org.apache.derby.drda.NetworkServerControl constructor in the API
> // or via the property derby.drda.host; the default is localhost.
> // You may want to restrict allowed hosts, e.g. to hosts in a specific
> // subdomain, e.g. "*.acme.com".
>   permission java.net.SocketPermission "*", "accept";
> </quote>
> See also 
> http://www.nabble.com/Customizing-the-Network-Server%27s-security-policy-%28docs-vs.-reality%29-td14841290.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to