Re: Java Security: JEP: 411: Deprecate the Security Manager for Removal - What about Serialization?

2021-05-03 Thread Peter Firmstone
Clarification inline below On 4/05/2021 8:35 am, Peter Firmstone wrote: On 4/05/2021 5:12 am, Sean Mullan wrote: -bcc jdk-dev -cc security-dev On 4/30/21 10:04 PM, Peter Firmstone wrote: In our software we use a ProtectionDomain to represent a remote server, because a thread only runs with

Re: Java Security: JEP: 411: Deprecate the Security Manager for Removal - What about Serialization?

2021-05-03 Thread Peter Firmstone
On 4/05/2021 5:12 am, Sean Mullan wrote: -bcc jdk-dev -cc security-dev On 4/30/21 10:04 PM, Peter Firmstone wrote: In our software we use a ProtectionDomain to represent a remote server, because a thread only runs with the user's Subject (and that Subject must be carefully preserved for oth

Re: Java Security: JEP: 411: Deprecate the Security Manager for Removal - What about Serialization?

2021-05-03 Thread Sean Mullan
-bcc jdk-dev -cc security-dev On 4/30/21 10:04 PM, Peter Firmstone wrote: Having had a day to think about this JEP, I have a simple request, I'd like to add to this JEP. Because those of us who require Access Control functionality will have to remain with a legacy version of Java until EOL an