Integrated: 8353642: Deprecate URL::getPermission method and networking permission classes for removal

2025-05-12 Thread Daniel Fuchs
On Fri, 11 Apr 2025 09:00:05 GMT, Daniel Fuchs wrote: > Please find her a patch that deprecate networking permission classes for > removal. The method `URL::getPermission` now serves little purpose and is > also deprecated. That method was overridden in subclasses and specified to

Re: RFR: 8353642: Deprecate URL::getPermission method and networking permission classes for removal [v4]

2025-05-12 Thread Daniel Fuchs
On Fri, 9 May 2025 19:19:03 GMT, Daniel Fuchs wrote: >> src/java.base/share/classes/java/net/HttpURLConnection.java line 615: >> >>> 613: */ >>> 614: @Deprecated(since = "25", forRemoval = true) >>> 615: @SuppressWarnings("remov

Re: RFR: 8353642: Deprecate URL::getPermission method and networking permission classes for removal [v4]

2025-05-12 Thread Daniel Fuchs
On Fri, 9 May 2025 19:18:58 GMT, Daniel Fuchs wrote: >> src/java.base/share/classes/sun/net/www/protocol/file/FileURLConnection.java >> line 214: >> >>> 212: */ >>> 213: @Override >>> 214: @Deprecated(since = "25", forRemoval

Re: RFR: 8353642: Deprecate URL::getPermission method and networking permission classes for removal [v4]

2025-05-09 Thread Daniel Fuchs
On Fri, 9 May 2025 16:42:31 GMT, Sean Mullan wrote: >> Daniel Fuchs has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contains five addi

Re: RFR: 8349910: Implement JEP 517: HTTP/3 for the HTTP Client API [v5]

2025-05-09 Thread Daniel Fuchs
350588) > > This JEP proposes to enhance the HttpClient implementation to support HTTP/3. > It adds a non-exposed / non-exported internal implementation of the QUIC > protocol based on DatagramChannel and the SunJSSE SSLContext provider. Daniel Fuchs has updated the pull request with a new

Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor

2025-05-09 Thread Daniel Fuchs
On Fri, 9 May 2025 08:40:44 GMT, Leo Korinth wrote: > The whole idea of running with a timeout factor of `0.7` is to remove > intermittent failures. (I had it close to 0.5 or maybe less to begin with > until I found and reported CODETOOLS-7903937: JTREG uses timeout factor on > socket timeout

Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor

2025-05-09 Thread Daniel Fuchs
On Thu, 8 May 2025 17:41:02 GMT, Daniel Fuchs wrote: > Thank you. I have imported your PR locally and running some HTTP client tests > in the CI. > Tests have not finished running - but I already see one intermittent failure: > `java/net/httpclient/RedirectTimeoutTest.java` i

Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor

2025-05-08 Thread Daniel Fuchs
On Thu, 8 May 2025 14:51:24 GMT, Leo Korinth wrote: > This change tries to add timeout to individual testcases so that I am able to > run them with a timeout factor of 1 in the future (JDK-8260555). > > The first commit changes the timeout factor to 0.7, so that I can run tests > and test the

Re: RFR: 8353642: Deprecate URL::getPermission method and networking permission classes for removal [v4]

2025-05-08 Thread Daniel Fuchs
> Please find her a patch that deprecate networking permission classes for > removal. The method `URL::getPermission` now serves little purpose and is > also deprecated. That method was overridden in subclasses and specified to > return some of the deprecated permissions. Dani

Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor

2025-05-08 Thread Daniel Fuchs
On Thu, 8 May 2025 14:51:24 GMT, Leo Korinth wrote: > This change tries to add timeout to individual testcases so that I am able to > run them with a timeout factor of 1 in the future (JDK-8260555). > > The first commit changes the timeout factor to 0.7, so that I can run tests > and test the

Re: RFR: 8353642: Deprecate URL::getPermission method and networking permission classes for removal [v4]

2025-05-08 Thread Daniel Fuchs
On Thu, 8 May 2025 16:10:18 GMT, Daniel Fuchs wrote: >> Please find her a patch that deprecate networking permission classes for >> removal. The method `URL::getPermission` now serves little purpose and is >> also deprecated. That method was overridden in subclasse

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API [v4]

2025-05-01 Thread Daniel Fuchs
rg/browse/JDK-8350588) > > This JEP proposes to enhance the HttpClient implementation to support HTTP/3. > It adds a non-exposed / non-exported internal implementation of the QUIC > protocol based on DatagramChannel and the SunJSSE SSLContext provider. Daniel Fuchs has updated the pull reques

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API [v3]

2025-04-30 Thread Daniel Fuchs
On Wed, 30 Apr 2025 10:19:54 GMT, Daniel Fuchs wrote: >> Hi, >> >> Please find here a PR for the implementation of JEP [JDK-8291976: HTTP/3 for >> the HTTP Client API](https://bugs.openjdk.org/browse/JDK-8291976). >> >> The CSR can be viewed at [JDK-83

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API [v3]

2025-04-30 Thread Daniel Fuchs
rg/browse/JDK-8350588) > > This JEP proposes to enhance the HttpClient implementation to support HTTP/3. > It adds a non-exposed / non-exported internal implementation of the QUIC > protocol based on DatagramChannel and the SunJSSE SSLContext provider. Daniel Fuchs has updated the pull reques

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API [v2]

2025-04-24 Thread Daniel Fuchs
rg/browse/JDK-8350588) > > This JEP proposes to enhance the HttpClient implementation to support HTTP/3. > It adds a non-exposed / non-exported internal implementation of the QUIC > protocol based on DatagramChannel and the SunJSSE SSLContext provider. Daniel Fuchs has updated the pull reques

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API

2025-04-22 Thread Daniel Fuchs
On Tue, 22 Apr 2025 18:48:06 GMT, Chen Liang wrote: >> PushId is an HTTP/3 concept. It would be strange to have a generic method >> (sendAsync) that you could call with any requests, but with a parameter that >> could only be used for HTTP/3. We don't have pushIds for HTTP/2. I don't >> think

Re: RFR: 8349910: Implement HTTP/3 for the HTTP Client API

2025-04-22 Thread Daniel Fuchs
On Fri, 18 Apr 2025 18:49:19 GMT, Chen Liang wrote: >> Hi, >> >> Please find here a PR for the implementation of JEP [JDK-8291976: HTTP/3 for >> the HTTP Client API](https://bugs.openjdk.org/browse/JDK-8291976). >> >> The CSR can be viewed at [JDK-8350588: Implement HTTP/3 for the HTTP Client

RFR: 8349910: Implement HTTP/3 for the HTTP Client API

2025-04-18 Thread Daniel Fuchs
Hi, Please find here a PR for the implementation of JEP [JDK-8291976: HTTP/3 for the HTTP Client API](https://bugs.openjdk.org/browse/JDK-8291976). The CSR can be viewed at [JDK-8350588: Implement HTTP/3 for the HTTP Client API](https://bugs.openjdk.org/browse/JDK-8350588) This JEP proposes to

Re: Integrated: Merge ed30fce6df57b1cbf7a6efebabc3558550f8ec16

2025-04-16 Thread Daniel Fuchs
On Wed, 16 Apr 2025 11:20:36 GMT, Jaikiran Pai wrote: > This brings in the CPU25_04 changes into the master branch. LGTM - Marked as reviewed by dfuchs (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/24683#pullrequestreview-2772164693

Re: RFR: 8348986: Improve coverage of enhanced exception messages [v6]

2025-04-15 Thread Daniel Fuchs
On Tue, 15 Apr 2025 14:35:28 GMT, Michael McMahon wrote: >> Hi, >> >> Enhanced exception messages are designed to hide sensitive information such >> as hostnames, IP >> addresses from exception message strings, unless the enhanced mode for the >> specific category >> has been explicitly enab

Re: RFR: 8348986: Improve coverage of enhanced exception messages [v5]

2025-04-14 Thread Daniel Fuchs
On Thu, 10 Apr 2025 21:26:21 GMT, Michael McMahon wrote: >> Hi, >> >> Enhanced exception messages are designed to hide sensitive information such >> as hostnames, IP >> addresses from exception message strings, unless the enhanced mode for the >> specific category >> has been explicitly enab

Re: RFR: 8353642: Deprecate URL::getPermission method and networking permission classes for removal [v2]

2025-04-11 Thread Daniel Fuchs
On Fri, 11 Apr 2025 13:47:10 GMT, Michael McMahon wrote: >> Daniel Fuchs has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Missing white spaces > > src/java.base/share/classes/java/security/CodeS

Re: RFR: 8353642: Deprecate networking permission classes for removal [v3]

2025-04-11 Thread Daniel Fuchs
> Please find her a patch that deprecate networking permission classes for > removal. The method `URL::getPermission` now serves little purpose and is > also deprecated. That method was overridden in subclasses and specified to > return some of the deprecated permissions. Dani

Re: RFR: 8353642: Deprecate URL::getPermission method and networking permission classes for removal [v2]

2025-04-11 Thread Daniel Fuchs
On Fri, 11 Apr 2025 11:47:21 GMT, Daniel Fuchs wrote: >> I think we should at least consider deprecating URLConnection.getPermission >> and HttpURLConnection.getPermission for removal, only because I don't >> immediately see the advantage of doing it in two steps for the

Re: RFR: 8353642: Deprecate URL::getPermission method and networking permission classes for removal [v2]

2025-04-11 Thread Daniel Fuchs
On Fri, 11 Apr 2025 12:31:04 GMT, Daniel Fuchs wrote: > The GHA failure (Windows) appears to be related. Should be fixed now - PR Comment: https://git.openjdk.org/jdk/pull/24592#issuecomment-2796995066

Re: RFR: 8353642: Deprecate networking permission classes for removal [v2]

2025-04-11 Thread Daniel Fuchs
On Fri, 11 Apr 2025 12:01:52 GMT, Daniel Jeliński wrote: > The GHA failure (Windows) appears to be related. Yes - I missed one windows specific file in my original patch. I have a test running in the CI and I am waiting for it to pass before updating the PR. - PR Comment: https://

Re: RFR: 8353642: Deprecate networking permission classes for removal [v2]

2025-04-11 Thread Daniel Fuchs
On Fri, 11 Apr 2025 11:34:36 GMT, Alan Bateman wrote: >> Possibly. @AlanBateman may have some thoughts on this. > > I think we should at least consider deprecating URLConnection.getPermission > and HttpURLConnection.getPermission for removal, only because I don't > immediately see the advantage

Re: RFR: 8353642: Deprecate networking permission classes for removal [v2]

2025-04-11 Thread Daniel Fuchs
On Fri, 11 Apr 2025 11:10:10 GMT, Daniel Jeliński wrote: >> src/java.base/share/classes/java/security/CodeSource.java line 468: >> >>> 466: } >>> 467: @SuppressWarnings("removal") >>> 468: var result = this.sp.implies(that.sp); >> >> Will we need

Re: RFR: 8353642: Deprecate networking permission classes for removal [v2]

2025-04-11 Thread Daniel Fuchs
On Fri, 11 Apr 2025 10:45:20 GMT, Daniel Jeliński wrote: >> Daniel Fuchs has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Missing white spaces > > src/java.base/share/classes/java/net/HttpURLConne

Re: RFR: 8353642: Deprecate networking permission classes for removal [v2]

2025-04-11 Thread Daniel Fuchs
> Please find her a patch that deprecate networking permission classes for > removal. The method `URL::getPermission` now serves little purpose and is > also deprecated. That method was overridden in subclasses and specified to > return some of the deprecated permissions. Dani

Re: RFR: 8353642: Deprecate networking permission classes for removal

2025-04-11 Thread Daniel Fuchs
On Fri, 11 Apr 2025 09:00:05 GMT, Daniel Fuchs wrote: > Please find her a patch that deprecate networking permission classes for > removal. The method `URL::getPermission` now serves little purpose and is > also deprecated. That method was overridden in subclasses and specified to

RFR: 8353642: Deprecate networking permission classes for removal

2025-04-11 Thread Daniel Fuchs
Please find her a patch that deprecate networking permission classes for removal. The method `URL::getPermission` now serves little purpose and is also deprecated. That method was overridden in subclasses and specified to return some of the deprecated permissions. - Commit message

Re: RFR: 8348967: Deprecate security permission classes for removal

2025-04-04 Thread Daniel Fuchs
On Fri, 4 Apr 2025 12:42:36 GMT, Sean Mullan wrote: > Please review this change to terminally deprecate the following security > related permission classes: `java.security.AllPermission`, > `java.security.UnresolvedPermission`, `javax.net.ssl.SSLPermission`, > `javax.security.auth.AuthPermissi

Re: RFR: 8348967: Deprecate security permission classes for removal

2025-04-04 Thread Daniel Fuchs
Hi David, Are there other subclasses of Permission that this framework uses? More specifically - would it be fine to deprecate NetPermission, URLPermission and SocketPermission classes? best regards, -- daniel On 04/04/2025 15:51, David M. Lloyd wrote: Can you elaborate or give an example/poi

Re: RFR: 8353641: Deprecate core library permission classes for removal

2025-04-04 Thread Daniel Fuchs
On Fri, 4 Apr 2025 12:37:32 GMT, Roger Riggs wrote: > Now that the Security Manager is permanently disabled, the following > permission classes in the core libraries area can be deprecated for removal > as they are no longer useful: FilePermission, LinkPermission, > LoggingPermission, Property

Re: RFR: 8349121: SSLParameters.setApplicationProtocols() ALPN example could be clarified [v3]

2025-02-06 Thread Daniel Fuchs
On Thu, 6 Feb 2025 19:47:54 GMT, Artur Barashev wrote: >> I still think that `Convert to the default ALPN encoding` comment is less >> confusing, we are just passing the string in the encoding that the library >> expects. Basically your comment assumes reader's familiarity with the RFC. > > `Co

Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid [v2]

2025-02-05 Thread Daniel Fuchs
request incrementally with one > additional commit since the last revision: > > Apply suggestions from cr > > Co-authored-by: Daniel Fuchs <67001856+df...@users.noreply.github.com> Marked as reviewed by dfuchs (Reviewer). - PR Review: https://git.openjdk.org/jdk/pull/23469#pullrequestreview-2596826422

Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid

2025-02-05 Thread Daniel Fuchs
On Wed, 5 Feb 2025 17:39:42 GMT, Mikhail Yankelevich wrote: > * fully automated the test > * removed the race condition > * client on a thread and server on a thread options are now run together > automatically And implementing the suggested changes would be good... - Changes requ

Re: RFR: 8249824: s/n/w/p/https/HttpsURLConnection/CloseKeepAliveCached.java uses @ignore w/o bugid

2025-02-05 Thread Daniel Fuchs
On Wed, 5 Feb 2025 17:39:42 GMT, Mikhail Yankelevich wrote: > * fully automated the test > * removed the race condition > * client on a thread and server on a thread options are now run together > automatically The new logic looks good to me. Please wait for a review from someone from security

Re: RFR: 8349121: SSLParameters.setApplicationProtocols() ALPN example could be clarified [v3]

2025-02-05 Thread Daniel Fuchs
On Tue, 4 Feb 2025 19:42:24 GMT, Bradford Wetmore wrote: >> Update and clarify the sample code. >> >> Docs only, no additional testing other than verifying javadoc is correctly >> output. > > Bradford Wetmore has updated the pull request incrementally with one > additional commit since the las

Re: RFR: 8349121: SSLParameters.setApplicationProtocols() ALPN example could be clarified [v3]

2025-02-05 Thread Daniel Fuchs
On Wed, 5 Feb 2025 17:42:11 GMT, Bradford Wetmore wrote: >> src/java.base/share/classes/javax/net/ssl/SSLParameters.java line 661: >> >>> 659: * // Encode 3 Meetei Mayek letters (HUK, UN, I) using Unicode >>> Escapes >>> 660: * // 0xabcd->0xabcf, 2 Unicode bytes/letter. >>

Re: RFR: 8349121: SSLParameters.setApplicationProtocols() ALPN example could be clarified [v3]

2025-02-05 Thread Daniel Fuchs
On Tue, 4 Feb 2025 19:42:24 GMT, Bradford Wetmore wrote: >> Update and clarify the sample code. >> >> Docs only, no additional testing other than verifying javadoc is correctly >> output. > > Bradford Wetmore has updated the pull request incrementally with one > additional commit since the las

Re: RFR: 8349121: SSLParameters.setApplicationProtocols() ALPN example could be clarified [v3]

2025-02-05 Thread Daniel Fuchs
On Wed, 5 Feb 2025 11:59:49 GMT, Daniel Fuchs wrote: >> Bradford Wetmore has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Codereview Comments > > src/java.base/share/classes/javax/net/ssl/SSLParam

Re: RFR: 8349121: SSLParameters.setApplicationProtocols() ALPN example could be clarified

2025-02-04 Thread Daniel Fuchs
On Fri, 31 Jan 2025 01:45:47 GMT, Bradford Wetmore wrote: > Update and clarify the sample code. > > Docs only, no additional testing other than verifying javadoc is correctly > output. src/java.base/share/classes/javax/net/ssl/SSLParameters.java line 668: > 666: * String encodedHukUn

Integrated: 8347597: HttpClient: improve exception reporting when closing connection

2025-01-15 Thread Daniel Fuchs
On Mon, 13 Jan 2025 16:07:45 GMT, Daniel Fuchs wrote: > There are a few places in the HttpClient code base where we close the > connection when some error/exception happens. This can some time trigger a > race condition where closing the connection in turns causes a "connec

Re: RFR: 8347597: HttpClient: improve exception reporting when closing connection [v2]

2025-01-14 Thread Daniel Fuchs
On Tue, 14 Jan 2025 09:52:59 GMT, Jaikiran Pai wrote: >> Daniel Fuchs has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Review feedback from @japai > > src/java.net.http/share/classes/jdk/internal/net/http/

Re: RFR: 8347597: HttpClient: improve exception reporting when closing connection [v2]

2025-01-14 Thread Daniel Fuchs
ption in the underlying > connection before closing it, and that this is the exception that gets > subsequently reported. > > Some minor drive by test fixes. No new regression test. Daniel Fuchs has updated the pull request incrementally with one additional commit since

RFR: 8347597: HttpClient: improve exception reporting when closing connection

2025-01-13 Thread Daniel Fuchs
There are a few places in the HttpClient code base where we close the connection when some error/exception happens. This can some time trigger a race condition where closing the connection in turns causes a "connection closed locally" exception to get reported instead of the original exception.

Re: RFR: 8346045: Cleanup of security library tests calling Security Manager APIs

2025-01-13 Thread Daniel Fuchs
On Mon, 13 Jan 2025 13:36:53 GMT, Sean Mullan wrote: > Some additional removal of calls to SM APIs from security library tests. One > test is removed since it is no longer an issue. Changes to SimpleSSLContext LGTM. Nice simplification! - PR Review: https://git.openjdk.org/jdk/pul

Re: RFR: 8347121: Add missing @serial tags to module java.base

2025-01-08 Thread Daniel Fuchs
On Wed, 8 Jan 2025 19:41:42 GMT, Hannes Wallnöfer wrote: > Please review a doc-only change to add missing `@serial` javadoc tags in > module `java.base`. This is a sub-task of [JDK-8286931] to allow us to > re-enable the javadoc `-serialwarn` option in the JDK doc build, which has > been disab

Re: RFR: 8346468: SM cleanup of common test library [v2]

2024-12-18 Thread Daniel Fuchs
On Wed, 18 Dec 2024 17:01:30 GMT, Roger Riggs wrote: >> SM Cleanup of common test library test/lib/...: >> >> Remove unnecessary catches of SecurityException >> Remove AccessController and doPrivileged from SimpleSSLContext and >> ProcessTools. > > Roger Riggs has updated the pull request incre

Re: RFR: 8346468: SM cleanup of common test library

2024-12-18 Thread Daniel Fuchs
On Wed, 18 Dec 2024 15:00:13 GMT, Roger Riggs wrote: > SM Cleanup of common test library test/lib/...: > > Remove unnecessary catches of SecurityException > Remove AccessController and doPrivileged from SimpleSSLContext and > ProcessTools. LGTM test/lib/jdk/test/lib/net/SimpleHttpServer.java

Re: RFR: 8345799: Update copyright year to 2024 for core-libs in files where it was missed [v2]

2024-12-09 Thread Daniel Fuchs
On Mon, 9 Dec 2024 13:03:06 GMT, Magnus Ihse Bursie wrote: >> Some files have been modified in 2024, but the copyright year has not been >> properly updated. This should be fixed. >> >> I have located these modified files using: >> >> git log --since="Jan 1" --name-only --pretty=format: | sor

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8]

2024-12-03 Thread Daniel Fuchs
On Tue, 3 Dec 2024 06:14:31 GMT, Jaikiran Pai wrote: >> src/java.base/linux/classes/jdk/internal/platform/CgroupSubsystemController.java >> line 68: >> >>> 66: try (Stream lines = Files.lines(filePath)) { >>> 67: Optional firstLine = lines.findFirst(); >>> 68: re

Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8]

2024-12-02 Thread Daniel Fuchs
On Mon, 2 Dec 2024 16:11:57 GMT, Jaikiran Pai wrote: >> Can I please get a review of this change which removes usages of >> SecurityManager related APIs and some leftover related to SecurityManager >> changes? >> >> This addresses https://bugs.openjdk.org/browse/JDK-8345286. Most of these >>

Re: RFR: 8344397: Remove Security Manager dependencies from java.security and sun.security packages [v5]

2024-12-02 Thread Daniel Fuchs
On Mon, 2 Dec 2024 18:12:55 GMT, Sean Mullan wrote: >> Now that JEP 486 has been integrated, `java.security` and `sun.security` >> implementation dependencies on `System.getSecurityManager` and >> `AccessController.doPrivileged` can be removed. >> >> This should cover most of the remaining cl

Re: RFR: 8344397: Remove Security Manager dependencies from java.security and sun.security packages [v2]

2024-11-28 Thread Daniel Fuchs
On Wed, 27 Nov 2024 19:59:24 GMT, Sean Mullan wrote: >> Now that JEP 486 has been integrated, `java.security` and `sun.security` >> implementation dependencies on `System.getSecurityManager` and >> `AccessController.doPrivileged` can be removed. >> >> This should cover most of the remaining c

Re: RFR: 8344299: SM cleanup in javax.naming modules [v3]

2024-11-28 Thread Daniel Fuchs
On Thu, 28 Nov 2024 17:28:59 GMT, Aleksei Efimov wrote: >> The proposed change cleans-up `SecurityManager`, `doPriviledged`, and >> `AccessController` usages from `java.naming`, `jdk.naming.rmi` and >> `jdk.naming.dns` modules. >> >> One noteworthy change: The `java.naming.rmi.security.manager

Re: RFR: 8344299: SM cleanup in javax.naming modules [v2]

2024-11-28 Thread Daniel Fuchs
On Thu, 28 Nov 2024 16:30:36 GMT, Alan Bateman wrote: >> Aleksei Efimov has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Remove com.sun.jndi.ldap.VersionHelper > > src/java.naming/share/classes/com/sun/jndi/ldap/LdapDnsProviderService.jav

Re: RFR: 8344299: SM cleanup in javax.naming modules [v2]

2024-11-28 Thread Daniel Fuchs
On Thu, 28 Nov 2024 13:58:58 GMT, Aleksei Efimov wrote: >> The proposed change cleans-up `SecurityManager`, `doPriviledged`, and >> `AccessController` usages from `java.naming`, `jdk.naming.rmi` and >> `jdk.naming.dns` modules. >> >> One noteworthy change: The `java.naming.rmi.security.manager

Re: RFR: 8344222: Remove calls to SecurityManager and doPrivileged in java.net.HttpURLConnection, java.net.HttpConnectSocketImpl, and javax.net.HttpsURLConnection after JEP 486 integration [v2]

2024-11-26 Thread Daniel Fuchs
On Mon, 25 Nov 2024 20:06:33 GMT, Volkan Yazıcı wrote: >> Addresses [8344222](https://bugs.openjdk.org/browse/JDK-8344222) and removes >> `SecurityManager` and `doPrivileged()` usages from `Http(s)URLConnection` >> and `HttpConnectSocketImpl`. `tier2` and `tier3` results are on their way. > > V

Re: RFR: 8344222: Remove calls to SecurityManager and doPrivileged in java.net.HttpURLConnection, java.net.HttpConnectSocketImpl, and javax.net.HttpsURLConnection after JEP 486 integration

2024-11-22 Thread Daniel Fuchs
On Fri, 22 Nov 2024 14:31:21 GMT, Volkan Yazıcı wrote: > Addresses [8344222](https://bugs.openjdk.org/browse/JDK-8344222) and removes > `SecurityManager` and `doPrivileged()` usages from `Http(s)URLConnection` and > `HttpConnectSocketImpl`. `tier2` and `tier3` results are on their way. LGTM -

Re: RFR: 8344652: Remove access control context text from SSLEngine and SSLSession APIs

2024-11-21 Thread Daniel Fuchs
On Thu, 21 Nov 2024 17:36:03 GMT, Sean Mullan wrote: > Some additional text in two `javax.net.ssl` APIs related to access control > context was missed as part of JEP 483. This behavior no longer applies now > that the Security Manager is permanently disabled and has been removed. > > The imple

Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration [v2]

2024-11-16 Thread Daniel Fuchs
On Sat, 16 Nov 2024 01:59:43 GMT, Jaikiran Pai wrote: >> Can I please get a review of this change which removes calls to >> `SecurityManager` and `AccessController.doPrivileged()` from the >> `ProxySelector` and `DefaultProxySelector` classes? >> >> Apart from the trivial removing of those cal

Re: RFR: 8344216: Remove calls to SecurityManager and and doPrivileged in java.net.Authenticator, java.net.CookieHandler, and java.net.ResponseCache after JEP 486 integration

2024-11-15 Thread Daniel Fuchs
On Fri, 15 Nov 2024 09:00:29 GMT, Eirik Bjørsnøs wrote: > Please review this PR to clean up SM use in `java.net.Authenticator`, > `java.net.CookieHandler`, and `java.net.ResponseCache` after JEP 486 > integration. > > * `Authenticator` is updated to remove calls to SM::checkPermission` > * `Co

Integrated: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration

2024-11-15 Thread Daniel Fuchs
On Thu, 14 Nov 2024 20:40:46 GMT, Daniel Fuchs wrote: > Please find here a patch that cleans up the java.net.http module code to > remove permission checks and doPriviliged calls. > This was mostly mechanical. This pull request has now been integrated. Changeset: 40a055eb Author:

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration [v4]

2024-11-15 Thread Daniel Fuchs
On Fri, 15 Nov 2024 09:10:51 GMT, Daniel Fuchs wrote: >> test/jdk/java/net/httpclient/whitebox/java.net.http/jdk/internal/net/http/SimpleSSLContext.java >> line 45: >> >>> 43: * Creates a simple usable SSLContext for SSLSocketFactory >>> 44: * or a HttpsSe

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration [v3]

2024-11-15 Thread Daniel Fuchs
On Fri, 15 Nov 2024 13:15:42 GMT, Jaikiran Pai wrote: >> Daniel Fuchs has updated the pull request with a new target base due to a >> merge or a rebase. The incremental webrev excludes the unrelated changes >> brought in by the merge/rebase. The pull request contain

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration [v4]

2024-11-15 Thread Daniel Fuchs
> Please find here a patch that cleans up the java.net.http module code to > remove permission checks and doPriviliged calls. > This was mostly mechanical. Daniel Fuchs has updated the pull request incrementally with one additional commit since the last revision: Jaikiran&#

Re: RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration

2024-11-15 Thread Daniel Fuchs
On Fri, 15 Nov 2024 10:31:11 GMT, Jaikiran Pai wrote: > Can I please get a review of this change which removes calls to > `SecurityManager` and `AccessController.doPrivileged()` from the > `ProxySelector` and `DefaultProxySelector` classes? > > Apart from the trivial removing of those calls, t

Re: RFR: 8344216: Remove calls to SecurityManager and and doPrivileged in java.net.Authenticator, java.net.CookieHandler, and java.net.ResponseCache after JEP 486 integration

2024-11-15 Thread Daniel Fuchs
On Fri, 15 Nov 2024 09:00:29 GMT, Eirik Bjørsnøs wrote: > Please review this PR to clean up SM use in `java.net.Authenticator`, > `java.net.CookieHandler`, and `java.net.ResponseCache` after JEP 486 > integration. > > * `Authenticator` is updated to remove calls to SM::checkPermission` > * `Co

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration [v3]

2024-11-15 Thread Daniel Fuchs
> Please find here a patch that cleans up the java.net.http module code to > remove permission checks and doPriviliged calls. > This was mostly mechanical. Daniel Fuchs has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration [v2]

2024-11-15 Thread Daniel Fuchs
> Please find here a patch that cleans up the java.net.http module code to > remove permission checks and doPriviliged calls. > This was mostly mechanical. Daniel Fuchs has updated the pull request incrementally with one additional commit since the last revision: Review

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration

2024-11-15 Thread Daniel Fuchs
On Thu, 14 Nov 2024 20:53:02 GMT, Michael McMahon wrote: >> Please find here a patch that cleans up the java.net.http module code to >> remove permission checks and doPriviliged calls. >> This was mostly mechanical. > > src/java.net.http/share/classes/jdk/internal/net/http/HttpClientBuilderImpl.

Re: RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration

2024-11-15 Thread Daniel Fuchs
On Thu, 14 Nov 2024 21:17:01 GMT, Michael McMahon wrote: >> Please find here a patch that cleans up the java.net.http module code to >> remove permission checks and doPriviliged calls. >> This was mostly mechanical. > > test/jdk/java/net/httpclient/whitebox/java.net.http/jdk/internal/net/http/Si

RFR: 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration

2024-11-14 Thread Daniel Fuchs
Please find here a patch that cleans up the java.net.http module code to remove permission checks and doPriviliged calls. This was mostly mechanical. - Commit messages: - 8344228: Revisit SecurityManager usage in java.net.http after JEP 486 integration Changes: https://git.openjdk

Re: RFR: 8344056: Use markdown format for man pages

2024-11-14 Thread Daniel Fuchs
On Wed, 13 Nov 2024 17:05:25 GMT, Magnus Ihse Bursie wrote: > Currently, the man pages are stored as troff (a text format) in the open > repo, and a content-wise identical copy is stored as markdown (another text > format) in the closed repo. > > Since markdown is preferred to troff in terms o

Re: RFR: 8343981: Remove usage of security manager from Thread and related classes [v4]

2024-11-12 Thread Daniel Fuchs
On Tue, 12 Nov 2024 18:47:46 GMT, Alan Bateman wrote: >> Removes the SecurityManager usage from Thread + friends. >> >> In Thread, the getContextClassLoader method is no longer caller-sensitive >> method. >> >> JavaLangAccess.newThreadWithAcc is removed and jdk.internal.access is no >> longer

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v6]

2024-11-03 Thread Daniel Fuchs
On Sat, 2 Nov 2024 22:25:06 GMT, ExE Boss 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 200 commits: >> >> - Merge remote-tracking branch 'jdk-sandbox/jep486' into JDK-8338411 >> - Modify three RMI tests

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v5]

2024-10-29 Thread Daniel Fuchs
On Tue, 29 Oct 2024 12:40:59 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v5]

2024-10-29 Thread Daniel Fuchs
On Tue, 29 Oct 2024 12:40:59 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v5]

2024-10-29 Thread Daniel Fuchs
On Tue, 29 Oct 2024 12:40:59 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v5]

2024-10-29 Thread Daniel Fuchs
On Tue, 29 Oct 2024 12:40:59 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v3]

2024-10-25 Thread Daniel Fuchs
On Thu, 24 Oct 2024 13:19:55 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v2]

2024-10-23 Thread Daniel Fuchs
On Wed, 23 Oct 2024 11:54:39 GMT, Alan Bateman 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 d

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v2]

2024-10-22 Thread Daniel Fuchs
On Tue, 22 Oct 2024 11:50:13 GMT, Michael McMahon 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 t

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v2]

2024-10-21 Thread Daniel Fuchs
On Fri, 18 Oct 2024 19:03:30 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v2]

2024-10-21 Thread Daniel Fuchs
On Fri, 18 Oct 2024 19:03:30 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: Merge 490d099e234f27adef7d691d3c5a08ebdb550c5d [v2]

2024-10-16 Thread Daniel Fuchs
On Wed, 16 Oct 2024 11:36:18 GMT, Jaikiran Pai wrote: >> This brings in CPU24_10 changes into master branch. > > Jaikiran Pai has updated the pull request with a new target base due to a > merge or a rebase. The incremental webrev excludes the unrelated changes > brought in by the merge/rebase.

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager

2024-10-15 Thread Daniel Fuchs
On Tue, 15 Oct 2024 16:34:40 GMT, Severin Gehwolf wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> mai

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager

2024-10-15 Thread Daniel Fuchs
On Tue, 15 Oct 2024 15:21:32 GMT, Alan Bateman wrote: >> src/java.logging/share/classes/java/util/logging/LogManager.java line 2430: >> >>> 2428: @Deprecated(since="17", forRemoval=true) >>> 2429: public void checkAccess() { >>> 2430: throw new SecurityException(); >> >> Though

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager

2024-10-15 Thread Daniel Fuchs
On Mon, 14 Oct 2024 13:52:24 GMT, Sean Mullan wrote: > This is the implementation of JEP 486: Permanently Disable the Security > Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The > [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the > main change

Re: RFR: 8241550: [macOS] SSLSocketImpl/ReuseAddr.java failed due to "BindException: Address already in use" [v2]

2024-05-28 Thread Daniel Fuchs
On Tue, 28 May 2024 01:46:01 GMT, Bradford Wetmore wrote: > It's too late now, but I might have suggested a short sleep between attempts. @bradfordwetmore what would be the rationale for that? If the ReuseAddr::run method throws BindException, then retrying immediately should hopefully let us

Integrated: 8241550: [macOS] SSLSocketImpl/ReuseAddr.java failed due to "BindException: Address already in use"

2024-05-24 Thread Daniel Fuchs
On Thu, 23 May 2024 08:42:00 GMT, Daniel Fuchs wrote: > This is one of these tests that is not really fixable if any other process > that might open a socket runs concurrently with it on the same machine: > nothing can guarantee that if you open a socket, close it, then open a new &g

Re: RFR: 8241550: [macOS] SSLSocketImpl/ReuseAddr.java failed due to "BindException: Address already in use" [v2]

2024-05-23 Thread Daniel Fuchs
ee. It might work most of > the time, but success can’t be guaranteed. > > The only thing we can do in order to attempt to minimize noisy intermittent > failures is retry the whole test if a BindException is thrown. Daniel Fuchs has updated the pull request incrementally with one addi

RFR: 8241550: [macOS] SSLSocketImpl/ReuseAddr.java failed due to "BindException: Address already in use"

2024-05-23 Thread Daniel Fuchs
This is one of these tests that is not really fixable if any other process that might open a socket runs concurrently with it on the same machine: nothing can guarantee that if you open a socket, close it, then open a new socket on the same port, that port will still be free. It might work most

Re: RFR: 8331671: Implement JEP 472: Prepare to Restrict the Use of JNI [v3]

2024-05-13 Thread Daniel Fuchs
On Mon, 13 May 2024 11:47:38 GMT, Maurizio Cimadamore wrote: >> This PR implements [JEP 472](https://openjdk.org/jeps/472), by restricting >> the use of JNI in the following ways: >> >> * `System::load` and `System::loadLibrary` are now restricted methods >> * `Runtime::load` and `Runtime::loa

Re: RFR: 8330178: Clean up non-standard use of /** comments in `java.base`

2024-04-19 Thread Daniel Fuchs
On Thu, 18 Apr 2024 20:44:00 GMT, Jonathan Gibbons wrote: > Please review a set of updates to clean up use of `/**` comments in the > vicinity of declarations. > > There are various categories of update: > > * "Box comments" beginning with `/**` > * Misplaced doc comments before package or imp

Re: RFR: Merge 33d7127

2024-04-17 Thread Daniel Fuchs
On Wed, 17 Apr 2024 01:09:30 GMT, Jaikiran Pai wrote: > This brings in the CPU24_04 changes. This looks reasonable. I haven't been involved in all the fixes here - but I haven't spotted anything obviously wrong. The changes to the ConnectionPool look right. If some of the fixes had conflicts t

Re: RFR: 8329013: StackOverflowError when starting Apache Tomcat with signed jar [v2]

2024-04-02 Thread Daniel Fuchs
On Tue, 2 Apr 2024 13:38:00 GMT, Daniel Fuchs wrote: >> Sean Coffey has updated the pull request incrementally with one additional >> commit since the last revision: >> >> incorporate testcase feedback from Daniel > > test/jdk/jdk/security/logging/RecursiveEven

  1   2   3   >