On Wed, 22 Dec 2021 01:18:58 GMT, Stuart Marks wrote:
>> Enable the security manager in rmiregistry's launcher arguments.
>
> Stuart Marks has updated the pull request incrementally with one additional
> commit since the last revision:
>
> Change java.security.manager to "allow"; filter warni
On Wed, 22 Dec 2021 01:18:58 GMT, Stuart Marks wrote:
>> Enable the security manager in rmiregistry's launcher arguments.
>
> Stuart Marks has updated the pull request incrementally with one additional
> commit since the last revision:
>
> Change java.security.manager to "allow"; filter warni
On Wed, 22 Dec 2021 01:18:58 GMT, Stuart Marks wrote:
>> Enable the security manager in rmiregistry's launcher arguments.
>
> Stuart Marks has updated the pull request incrementally with one additional
> commit since the last revision:
>
> Change java.security.manager to "allow"; filter warni
> Enable the security manager in rmiregistry's launcher arguments.
Stuart Marks has updated the pull request incrementally with one additional
commit since the last revision:
Change java.security.manager to "allow"; filter warning lines from
VersionCheck
-
Changes:
- all: http
On Sun, 19 Dec 2021 07:37:19 GMT, Alan Bateman wrote:
>> Enable the security manager in rmiregistry's launcher arguments.
>
> As things stand, `rmiregsitry -J-Djava.security.manager` and `rmiregistry
> -J-Djava.security.manager=allow` are equivalent because rmiregistry sets the
> default SM. So
On Fri, 17 Dec 2021 20:01:27 GMT, Stuart Marks wrote:
> Enable the security manager in rmiregistry's launcher arguments.
I think there's little to worry about with custom configurations of the
`rmiregistry` tool. What somebody might do is to enable a customized security
manager using propertie
On Fri, 17 Dec 2021 20:01:27 GMT, Stuart Marks wrote:
> Enable the security manager in rmiregistry's launcher arguments.
As things stand, `rmiregsitry -J-Djava.security.manager` and `rmiregistry
-J-Djava.security.manager=allow` are equivalent because rmiregistry sets the
default SM. Some diffe
