<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Peter Firmstone on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/peter-firmstone/</link><description>Articles written by Peter Firmstone on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 03 Jun 2021 07:47:51 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/peter-firmstone/index.xml" rel="self" type="application/rss+xml"/><item><title>JEP 411: Java's Security Model and the Principle of Least Privilege</title><link>https://foojayio.github.io/website/today/jep-411-what-it-means-for-javas-security-model/</link><pubDate>Thu, 03 Jun 2021 07:47:51 +0000</pubDate><guid>https://foojayio.github.io/website/today/jep-411-what-it-means-for-javas-security-model/</guid><description>&lt;p&gt;&lt;img src="https://upload.wikimedia.org/wikipedia/commons/0/07/Swiss_cheese_model.svg" alt="" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;Java, like most platforms or languages has layers of security, this article intends to look at Java&amp;rsquo;s Authorization layer, which is unlike in other languages, and to distinguish between two different ways this layer is typically utilized, why one is effective while the other isn&amp;rsquo;t and investigate why JEP 411 only considers the least effective method and hopefully increase awareness of the Principle of Least Privilege as it&amp;rsquo;s applied to Java Authorization, improve adoption, encourage people to take advantage of the improved security it provides, as well as prolong its support and possibly even improve it in future.&lt;/p&gt;</description></item><item><title>Why JEP 411 Will Have a Negative Impact on Java Security</title><link>https://foojayio.github.io/website/today/why-jep-411-will-have-a-negative-impact-on-java-security/</link><pubDate>Sat, 22 May 2021 07:43:06 +0000</pubDate><guid>https://foojayio.github.io/website/today/why-jep-411-will-have-a-negative-impact-on-java-security/</guid><description>&lt;p&gt;&lt;em&gt;&lt;a href="https://openjdk.java.net/jeps/411" target="_blank" rel="noopener noreferrer"&gt;JEP 411&lt;/a&gt;
 specifies the &amp;ldquo;deprecation of the Security Manager for removal in a future release. The Security Manager dates from Java 1.0. It has not been the primary means of securing client-side Java code for many years, and it has rarely been used to secure server-side code. To move Java forward, we intend to deprecate the Security Manager for removal in concert with the legacy Applet API (JEP 398).&amp;rdquo; Below, Peter Firmstone describes how this relates to the principle of least privilege and what the impact of this JEP will be. Agree or disagree, add your comments, or your full articles on this topic are also welcome here on Foojay.&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>