RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v2]
Harshitha Onkar
honkar at openjdk.org
Tue Oct 22 20:58:31 UTC 2024
On Tue, 22 Oct 2024 08:16:38 GMT, Prasanta Sadhukhan <psadhukhan at openjdk.org> wrote:
>> Sean Mullan has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 97 commits:
>>
>> - Merge remote-tracking branch 'jdk-sandbox/jep486' into JDK-8338411
>> - Change apiNote to deprecated annotation on checkAccess methods. Change method dedescription to "Does nothing".
>> - Sanitize the class descriptions of DelegationPermission and ServicePermission
>> by removing text that refers to granting permissions, but avoid changes that
>> affect the API specification, such as the description and format of input
>> parameters.
>> - Restored methods in RMIConnection to throw SecurityExceptions again but
>> with adjusted text that avoids the word "permission".
>> - Add text to class description of MBeanServer stating that implementations
>> may throw SecurityException if authorization doesn't allow access to resource.
>> - Restore text about needing permissions from the desktop environment in the
>> getPixelColor and createScreenCapture methods.
>> - Add api note to getClassContext to use StackWalker instead and
>> add DROP_METHOD_INFO option to StackWalker.
>> - Change checkAccess() methods to be no-ops, rather than throwing
>> SecurityException.
>> - Merge
>> - Merge
>> - ... and 87 more: https://git.openjdk.org/jdk/compare/f50bd0d9...f89d9d09
>
> test/jdk/javax/swing/JEditorPane/8080972/TestJEditor.java line 49:
>
>> 47: SwingUtilities.invokeAndWait(TestJEditor::testJEditorPane);
>> 48: }
>> 49:
>
> Is there any need to catch the exception and rethrow RuntimeException below? I think we can remove try-catch block altogether...
Updated
> test/jdk/javax/swing/JPopupMenu/6691503/bug6691503.java line 48:
>
>> 46: test.setupUI();
>> 47: test.testApplication();
>> 48: test.testApplet();
>
> I guess we can only remove this `testApplet` as SM is invoked there only....we can still test `testApplication`, right?
Updated. Repurposed the test.
> test/jdk/javax/swing/JPopupMenu/6694823/bug6694823.java line 117:
>
>> 115: }
>> 116: popup.setVisible(false);
>> 117: frame.dispose();
>
> The error condition is checked and exception thrown before disposing the frame and popup, guess this 2 should be in finally block..
Updated
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/21498#discussion_r1811381885
PR Review Comment: https://git.openjdk.org/jdk/pull/21498#discussion_r1811382077
PR Review Comment: https://git.openjdk.org/jdk/pull/21498#discussion_r1811382336
More information about the build-dev
mailing list