Re: How to remove the SecurityManager

2021-07-27 Thread Peter Firmstone
On 28/07/2021 9:12 am, Peter Firmstone wrote: While its possible to use a dynamic proxy without downloading code, via an atomic serialization connection, it's not generally advised to do so with unauthenticated users, decisions around dynamic discovery, whether class loading or downloads are a

Re: How to remove the SecurityManager

2021-07-27 Thread Peter Firmstone
Thanks Remi, Sand-boxing is a bad idea, we are in agreement, it's not something we do, personally I'm taking an interest in safer languages, eg Haskell on secure platforms, eg OpenBSD on Sparc64 *. Perhaps JEP 411 is simply a reflection on the evolution of languages.  Java was safer than C a

Integrated: 8267485: Remove the dependency on SecurityManager in JceSecurityManager.java

2021-07-27 Thread Bradford Wetmore
On Sat, 22 May 2021 00:20:11 GMT, Bradford Wetmore wrote: > The JceSecurityManager is currently a subclass of > java.security.SecurityManager. Now that JEP 411 has been integrated, this > class should be updated to no longer subclass SecurityManager. > > The only reason for using SecurityMana

Integrated: 8270946: X509CertImpl.getFingerprint should not return the empty String

2021-07-27 Thread Sean Mullan
On Fri, 23 Jul 2021 17:16:26 GMT, Sean Mullan wrote: > Please review this fix to change the internal `X509CertImpl.getFingerprint` > method to not return "" as a fingerprint if there is an error generating that > fingerprint. Instead, `null` is now returned, and "" is no longer cached as a > v

Re: RFR: 8267485: Remove the dependency on SecurityManager in JceSecurityManager.java [v8]

2021-07-27 Thread Sean Mullan
On Tue, 27 Jul 2021 05:43:53 GMT, Bradford Wetmore wrote: >> The JceSecurityManager is currently a subclass of >> java.security.SecurityManager. Now that JEP 411 has been integrated, this >> class should be updated to no longer subclass SecurityManager. >> >> The only reason for using Securit