Peter Firmstone continues his series on #Security on the #JVM.
Part 1 declared constraints on a remote call. Part 2 vetted code before a client loaded it. Part 3 and 4 established who is calling and carried that chain across the wire. Part 5 decided what the combination is allowed to do. This last part is about what all of it costs.
#DirtyChai scales vertically, inside one JVM. #JGDMS scales horizontally, across a fleet of them.
Guest author Peter Firmstone continues his brilliant series of #Security baked into the #JVM, with his third post: two Subjects, one call
This part covers the two kinds of identity a call carries, how SPIFFE manages process credentials without keystores, and how three identity layers coexist on a single dispatch thread.
Guest author Peter Firmstone continues to explore and analyze the theme of #Security Baked Into the #JVM.
Today's focus is on multi-Subject dispatch: how up to sixteen user Subjects cross a call on the #JERI wire, why the receiver believes none of them on principle, and how the chain survives a thread boundary and a distributed transaction.
Guest author Peter Firmstone continues his exploration of #security baked into the #JVM.
This 5th part is about what the caller is then allowed to do:
how incoming arguments are validated before they become objects,
why permissions are granted to what the code is, rather than where it came from,
how three policy layers combine so that no single party can widen its own authority.
