# Security Baked Into the JVM: why fork Apache River and OpenJDK?

DevFeed: [Security Baked Into the JVM: why fork Apache River and OpenJDK?](<https://devfeed.tech/articles/security-baked-into-the-jvm-why-fork-apache-river-and-openjdk-18928.md>)

Original publisher: [Read original article](<https://blog.frankel.ch/security-baked-into-jvm/1/>)

Author: Peter Firmstone

Published: 2026-06-28T00:00:00Z

Content type: article

Language: en

Sources: [Nicolas Fränkel](<https://devfeed.tech/sources/nicolas-frankel.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [jini](<https://devfeed.tech/topics/jini.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Data serialization](<https://devfeed.tech/topics/data-serialization.md>), [Network](<https://devfeed.tech/topics/network.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [code](<https://devfeed.tech/tags/code.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [dirtychai](<https://devfeed.tech/tags/dirtychai.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [fork](<https://devfeed.tech/tags/fork.md>), [inside](<https://devfeed.tech/tags/inside.md>), [java](<https://devfeed.tech/tags/java.md>), [java-17](<https://devfeed.tech/tags/java-17.md>), [jgdms](<https://devfeed.tech/tags/jgdms.md>), [jini](<https://devfeed.tech/tags/jini.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [network](<https://devfeed.tech/tags/network.md>), [network-firewall](<https://devfeed.tech/tags/network-firewall.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [security](<https://devfeed.tech/tags/security.md>), [technical](<https://devfeed.tech/tags/technical.md>), [third-party](<https://devfeed.tech/tags/third-party.md>), [trust](<https://devfeed.tech/tags/trust.md>), [trust-boundaries](<https://devfeed.tech/tags/trust-boundaries.md>)

## AI overview

The excerpt presents DirtyChai and JGDMS as separate projects designed to work together after Java's SecurityManager removal left applications that load remote code without built-in JVM authorization controls. DirtyChai is a community OpenJDK fork that restores authorization infrastructure and is required to run JGDMS; it adds virtual-thread support and a lock-free policy engine within one JVM. JGDMS is a security-hardened Apache River fork for dynamically discovering microservices over IPv6. It uses lease-based Jini-style discovery, JERI for pluggable constraint-based RPC, and layered protections including hardened deserialization, TLS 1.3, authorization, proxy trust checks, and bytecode analysis before loading. The excerpt introduces a deployment example but does not provide its steps.

## Source excerpt

The more distributed a system, the harder it is to secure. Code crosses JVM boundaries. Objects are serialized across trust boundaries. Third-party proxies run inside your process. The usual answer is a network firewall. It helps, but it operates at the wrong level. Java 17 deprecated the SecurityManager, Java 24 put the final nail in its coffin. Most developers didn't notice.