| [427] | 1 | .TH policyeditor 1 "10 Mar 2014"
|
|---|
| 2 |
|
|---|
| 3 | .SH NAME
|
|---|
| 4 |
|
|---|
| 5 | policyeditor - view and modify security policy settings for
|
|---|
| 6 | .B javaws
|
|---|
| 7 | and the browser plugin
|
|---|
| 8 |
|
|---|
| 9 | .SH SYNOPSIS
|
|---|
| 10 |
|
|---|
| 11 | .B policyeditor
|
|---|
| 12 | .br
|
|---|
| 13 | .B policyeditor [-file]
|
|---|
| 14 | policy_file
|
|---|
| 15 | .B [-codebase]
|
|---|
| 16 | url
|
|---|
| 17 | .SH DESCRIPTION
|
|---|
| 18 | .B policyeditor
|
|---|
| 19 | is a GUI application with small command line support to view and edit applet security policy settings
|
|---|
| 20 | used by the icedtea-web implementation of
|
|---|
| 21 | .B javaws
|
|---|
| 22 | and the browser plugin. It is intended as a simpler, easier to use, and more
|
|---|
| 23 | accessible alternative to the standard JDK Policy Tool. Administrators and
|
|---|
| 24 | power users who need fine grained control over policy files should probably
|
|---|
| 25 | use Policy Tool instead of PolicyEditor.
|
|---|
| 26 |
|
|---|
| 27 | If executed without any arguments, no file is opened, and saving the file will
|
|---|
| 28 | result in a prompt on where to save it. Otherwise, if a file path is given as
|
|---|
| 29 | a command line argument, then that file path will be opened and parsed as a
|
|---|
| 30 | policy file.
|
|---|
| 31 |
|
|---|
| 32 |
|
|---|
| 33 | .SH OPTIONS
|
|---|
| 34 |
|
|---|
| 35 | .TP
|
|---|
| 36 | -help
|
|---|
| 37 | Prints a short help text and exits.
|
|---|
| 38 |
|
|---|
| 39 | .TP
|
|---|
| 40 | -file policy_file
|
|---|
| 41 | Specifies a policy file path to open. If exactly one argument is given, and it
|
|---|
| 42 | is not this flag, it is interpreted as a file path to open, as if this flag
|
|---|
| 43 | was given first. This flag exists mostly for compatibility with Policy Tool,
|
|---|
| 44 | but is also needed when opening a policy file and also using the -codebase flag.
|
|---|
| 45 |
|
|---|
| 46 | .TP
|
|---|
| 47 | -codebase url
|
|---|
| 48 | Specifies an applet codebase URL. If the specified codebase already exists in
|
|---|
| 49 | the policy file (if any), then it will be selected when the editor opens. If
|
|---|
| 50 | it is a new codebase then it will be added and selected. Multiple URLs may also
|
|---|
| 51 | be given with a single -codebase flag by separating them with spaces. In this
|
|---|
| 52 | case, the last codebase given will be selected, and all will be added. If this
|
|---|
| 53 | flag is given more than once, only the first is used.
|
|---|
| 54 |
|
|---|
| 55 | .SH EXAMPLES
|
|---|
| 56 |
|
|---|
| 57 | .TP
|
|---|
| 58 | policyeditor
|
|---|
| 59 | Show the GUI editor
|
|---|
| 60 |
|
|---|
| 61 | .TP
|
|---|
| 62 | policyeditor -file $HOME/.config/icedtea-web/security/java.policy
|
|---|
| 63 | Opens the default user-level policy file location
|
|---|
| 64 |
|
|---|
| 65 |
|
|---|
| 66 | .SH FILES
|
|---|
| 67 |
|
|---|
| 68 | $HOME/.config/icedtea-web/security/java.policy the default user-level policy file location
|
|---|
| 69 |
|
|---|
| 70 | .SH BUGS
|
|---|
| 71 |
|
|---|
| 72 | There aren't any known bugs. If you come across one, please file it at
|
|---|
| 73 | http://icedtea.classpath.org/bugzilla/
|
|---|
| 74 |
|
|---|
| 75 | .SH AUTHOR
|
|---|
| 76 |
|
|---|
| 77 | Written and maintained by the IcedTea contributors.
|
|---|
| 78 |
|
|---|
| 79 | .SH SEE ALSO
|
|---|
| 80 |
|
|---|
| 81 | .BR policytool (1),
|
|---|
| 82 | .BR javaws (1),
|
|---|
| 83 | .BR java (1)
|
|---|
| 84 | .br
|
|---|
| 85 | http://icedtea.classpath.org/wiki/IcedTea-Web
|
|---|
