--- old/src/java.base/share/classes/java/security/SecurityPermission.java 2017-07-11 14:33:51.392892142 -0700 +++ new/src/java.base/share/classes/java/security/SecurityPermission.java 2017-07-11 14:33:51.192883414 -0700 @@ -49,15 +49,15 @@ * target name, what the permission allows, and associated risks * * - * Permission Target Name - * What the Permission Allows - * Risks of Allowing this Permission + * Permission Target Name + * What the Permission Allows + * Risks of Allowing this Permission * * * * * - * authProvider.{provider name} + * authProvider.{provider name} * Allow the named provider to be an AuthProvider for login and * logout operations. * This allows the named provider to perform login and logout @@ -68,7 +68,7 @@ * * * - * createAccessControlContext + * createAccessControlContext * Creation of an AccessControlContext * This allows someone to instantiate an AccessControlContext * with a {@code DomainCombiner}. Extreme care must be taken when @@ -78,7 +78,7 @@ * * * - * getDomainCombiner + * getDomainCombiner * Retrieval of an AccessControlContext's DomainCombiner * This allows someone to retrieve an AccessControlContext's * {@code DomainCombiner}. Since DomainCombiners may contain @@ -86,7 +86,7 @@ * * * - * getPolicy + * getPolicy * Retrieval of the system-wide security policy (specifically, of the * currently-installed Policy object) * This allows someone to query the policy via the @@ -99,7 +99,7 @@ * * * - * setPolicy + * setPolicy * Setting of the system-wide security policy (specifically, * the Policy object) * Granting this permission is extremely dangerous, as malicious @@ -108,7 +108,7 @@ * * * - * createPolicy.{policy type} + * createPolicy.{policy type} * Getting an instance of a Policy implementation from a provider * Granting this permission enables code to obtain a Policy object. * Malicious code may query the Policy object to determine what permissions @@ -116,7 +116,7 @@ * * * - * getProperty.{key} + * getProperty.{key} * Retrieval of the security property with the specified key * Depending on the particular key for which access has * been granted, the code may have access to the list of security @@ -129,7 +129,7 @@ * * * - * setProperty.{key} + * setProperty.{key} * Setting of the security property with the specified key * This could include setting a security provider or defining * the location of the system-wide security policy. Malicious @@ -144,7 +144,7 @@ * * * - * insertProvider + * insertProvider * Addition of a new provider * This would allow somebody to introduce a possibly * malicious provider (e.g., one that discloses the private keys passed @@ -158,7 +158,7 @@ * * * - * removeProvider.{provider name} + * removeProvider.{provider name} * Removal of the specified provider * This may change the behavior or disable execution of other * parts of the program. If a provider subsequently requested by the @@ -171,7 +171,7 @@ * * * - * clearProviderProperties.{provider name} + * clearProviderProperties.{provider name} * "Clearing" of a Provider so that it no longer contains the properties * used to look up services implemented by the provider * This disables the lookup of services implemented by the provider. @@ -181,7 +181,7 @@ * * * - * putProviderProperty.{provider name} + * putProviderProperty.{provider name} * Setting of properties for the specified Provider * The provider properties each specify the name and location * of a particular service implemented by the provider. By granting @@ -190,7 +190,7 @@ * * * - * removeProviderProperty.{provider name} + * removeProviderProperty.{provider name} * Removal of properties from the specified Provider * This disables the lookup of services implemented by the * provider. They are no longer accessible due to removal of the properties @@ -213,15 +213,15 @@ * target name, what the permission allows, and associated risks * * - * Permission Target Name - * What the Permission Allows - * Risks of Allowing this Permission + * Permission Target Name + * What the Permission Allows + * Risks of Allowing this Permission * * * * * - * insertProvider.{provider name} + * insertProvider.{provider name} * Addition of a new provider, with the specified name * Use of this permission is discouraged from further use because it is * possible to circumvent the name restrictions by overriding the @@ -238,7 +238,7 @@ * * * - * setSystemScope + * setSystemScope * Setting of the system identity scope * This would allow an attacker to configure the system identity scope with * certificates that should not be trusted, thereby granting applet or @@ -247,7 +247,7 @@ * * * - * setIdentityPublicKey + * setIdentityPublicKey * Setting of the public key for an Identity * If the identity is marked as "trusted", this allows an attacker to * introduce a different public key (e.g., its own) that is not trusted @@ -257,7 +257,7 @@ * * * - * setIdentityInfo + * setIdentityInfo * Setting of a general information string for an Identity * This allows attackers to set the general description for * an identity. This may trick applications into using a different @@ -266,7 +266,7 @@ * * * - * addIdentityCertificate + * addIdentityCertificate * Addition of a certificate for an Identity * This allows attackers to set a certificate for * an identity's public key. This is dangerous because it affects @@ -275,7 +275,7 @@ * * * - * removeIdentityCertificate + * removeIdentityCertificate * Removal of a certificate for an Identity * This allows attackers to remove a certificate for * an identity's public key. This is dangerous because it affects @@ -284,7 +284,7 @@ * * * - * printIdentity + * printIdentity * Viewing the name of a principal * and optionally the scope in which it is used, and whether * or not it is considered "trusted" in that scope @@ -296,7 +296,7 @@ * * * - * getSignerPrivateKey + * getSignerPrivateKey * Retrieval of a Signer's private key * It is very dangerous to allow access to a private key; private * keys are supposed to be kept secret. Otherwise, code can use the @@ -305,7 +305,7 @@ * * * - * setSignerKeyPair + * setSignerKeyPair * Setting of the key pair (public key and private key) for a Signer * This would allow an attacker to replace somebody else's (the "target's") * keypair with a possibly weaker keypair (e.g., a keypair of a smaller