Episódios

  • Security Is Your Job: OWASP, AI and Safer Java Dependencies with Jim Manico (Foojay Podcast #105)
    Nov 14 2026

    How safe is your Java application, and how safe are the dependencies it ships with? If you build software that handles sensitive data and you have no security process, OWASP's Jim Manico has a blunt word for it: negligent.

    In this episode, Jim Manico, founder of Manicode Security, Java Champion and OWASP project leader, explains what OWASP is and which of its projects matter to Java developers. He brought the OWASP Java Encoder, Java HTML Sanitizer and JSON Sanitizer back to life with AI-assisted workflows, and tells us what he learned along the way.

    Topics include:

    • When to use the OWASP Java Encoder versus the Java HTML Sanitizer
    • Why untrusted input must be checked on both the client and the server
    • How a few kilobytes of nested CSS can cause a denial-of-service
    • Why chained small vulnerabilities become a major one in the age of AI
    • Why Jim wants far fewer third-party libraries, and how to keep the rest up to date
    • What to do first when your team has no security process


    Guest: Jim Manico
    Founder of Manicode Security, Java Champion and OWASP project leader
    Jim on LinkedIn


    Links:

    Full show notes with all links
    OWASP Java Security Libraries: Please Update
    OWASP Java Encoder
    OWASP Java HTML Sanitizer
    trim-reaper on GitHub


    Timestamps:
    00:00 Introduction of topic and guest
    02:11 What is OWASP?
    04:10 How AI influences the speed of OWASP changes. Who contributes.
    06:30 Which OWASP projects you should know as a Java developer
    07:30 How Jim uses AI to evolve his libraries
    08:28 When to use OWASP Java Encoder and OWASP Java HTML Sanitizer
    13:58 User input needs to be checked in all steps (UI and backend)
    16:07 Man-in-the-middle attacks (eMuhdra)
    17:17 How to keep your systems up-to-date + minimize your dependencies
    22:34 How CSS can cause a denial-of-service problem
    24:52 How multiple small security issues can be combined into a major issue
    26:36 How to handle the growing number of discovered vulnerabilities
    29:13 The era of coding is coming to an end but you can still be a master developer
    32:45 How to automate upgrading with Maven, Gradle, and other tools
    36:42 What Java developers can learn from recent security problems (like PHP and eMuhdra)
    38:42 You must have a security process! Make your managers aware...
    43:53 How to get involved in OWASP
    46:08 What to remember from this podcast: security is your responsibility!

    Exibir mais Exibir menos
    49 minutos
  • 53 CVEs and Two Emergency Releases: Why Java Security Holds Up (#104)
    Oct 31 2026

    A record 53 CVEs in one Java update, followed by two emergency releases within days. Yes, a lot of issues are being found, but Java is still strong: a whole community and the commercial distributors are behind every fix.

    In this episode, Simon Ritter, Deputy CTO at Azul, Java Champion and member of the OpenJDK Vulnerability Group, explains what happened over the past weeks and what it means for your applications. We cover how a vulnerability travels from a report to a patch, why AI is changing the number of fixes, and why you should be ready to update at any moment. If you want to understand how CVEs are handled behind the scenes and what the different types of security updates mean, this episode explains it.

    Topics include:

    • What a CVE and a CVSS score really tell you, and why low scores can be chained into serious attacks
    • How vulnerabilities are kept secret and encrypted in the OpenJDK Vulnerability Group until a patch exists
    • Why the average of 7.6 CVEs per quarter jumped to 53, and the move toward monthly security updates
    • The eMudhra certificate problem and the two out-of-cycle releases that followed
    • The backporting workload behind every supported Java version, from 27 down to 6
    • CPU, PSU and CSPU explained, and what free versus paid OpenJDK builds mean for your patching


    Guest: Simon Ritter
    Deputy CTO at Azul and Java Champion
    Simon on LinkedIn

    Links:


    Full show notes with all links
    Free Java, Real Risk: Why Unsupported OpenJDK Is Now a Security Gamble
    Azul Zulu October 2026 Quarterly Update and Out-of-Cycle Release


    Timestamps:
    00:00 Introduction of topic and guest
    01:59 What is a CVE and how are they reported and handled?
    08:45 How the Java security release cycle is changing and each have more CVEs
    11:48 How AI impacts the discovery of CVEs
    14:09 What was the eMudhra problem causing two out-of-cycle security updates?
    21:49 The impact of creating an out-of-cycle update (and backports)
    26:05 How safe will OpenJDK builds be in the future? And dependencies?
    29:06 Free versus paid versions of OpenJDK builds
    32:40 CPU vs PSU vs CSPU: the names used for different types of security updates (security only versus including patches)
    35:52 What will happen with old Java versions like 6, 7, 8
    37:05 Why would you pay for a supported OpenJDK build?
    41:50 Conclusion: check your Java version and be ready to update at any moment!

    Exibir mais Exibir menos
    44 minutos
  • Killing Reflection at Build Time: Avro, Codename One and Java Codegen (#103)
    Oct 17 2026

    Runtime reflection is a quiet tax on the JVM. It is flexible, it is everywhere, and it is easy to stop noticing it until you go looking for where your CPU is actually going. Two teams did exactly that, in completely different corners of the ecosystem, and arrived at the same answer: move the work to build time.

    In this episode, Dmitry Moskalyuk explains the model layer behind his Foojay article on reflection-free serialization, where JSON, XML, YAML and TOML all end up as Avro. Shai Almog explains the build-time codegen pipeline of Codename One, which aims for no reflection, no service loader and no Class.forName. We compare the two and ask whether generated code is really something to avoid.

    Topics include:

    • Where Jackson's reflection cost really lives, and what Blackbird does about it
    • Jackson versus kotlinx.serialization, and why a missing feature sent the team back to Jackson
    • Why a UI framework bans reflection, and how that differs from the backend
    • Is generated code bad? Lombok, Manifold and jOOQ
    • What Records and Project Leyden change for reflection
    • Build time cost versus runtime cost, and a single source of truth for your data model
    • Should you still use reflection in a new project?


    Guests:
    Dmitry Moskalyuk, Senior Backend Engineer
    Dmitry on LinkedIn
    Shai Almog, Author, DevRel and open source developer working on Codename One
    Shai on LinkedIn

    Links:

    Dmitry's article on Foojay
    Shai's article on Foojay
    Jackson Blackbird
    Apache Avro
    Project Leyden
    Full show notes with every link

    Timestamps:
    00:00 Introduction of topic and guests
    01:50 About the new Foojay, contributing with GitHub pull requests
    03:17 What is Apache Avro
    04:26 What is Codename One
    06:31 What is Blackbird in Jackson and compared to kotlinx mechanisms for different content parsers
    10:01 Why Codename One focuses on "no reflection, no service loader, no Class.forName"
    14:23 Is automatically generated code bad (Lombok, Manifold, JOOQ)?
    17:47 Java evolutions that bring improvements into the system (Records, Project Leyden)
    21:31 Is reflection changing through Java versions?
    24:29 Build time cost versus runtime, Project Leyden
    28:41 Use of reflection in UI versus backend
    32:16 Benefit of your data model in a (Java) object, having one source of truth, good debugging
    35:35 Should you worry about serialization in a small project
    37:38 Serialization and security
    38:57 Should I still use reflection/serialization in a new project?
    43:22 Conclusion

    Exibir mais Exibir menos
    45 minutos
  • We Left WordPress: CMS vs Static Sites, Hugo vs Jekyll vs Roq (#102)
    Oct 3 2026

    Foojay.io quietly moved off WordPress and onto Hugo. No more CMS login, no database, no admin panel — just Markdown and AsciiDoc files, built and deployed straight from GitHub. So is a traditional CMS still the right way to run a content site in 2026, or has static tooling caught up?

    In this episode, Andy Damevin and Holly Cummins from the Red Hat Quarkus team join to talk through it. Andy created code.quarkus.io and Roq, Quarkus's own Java-based static site framework; Holly led the migration of quarkus.io itself from Jekyll to Roq. We go through the real security numbers behind WordPress's plugin ecosystem, and put very different static site generators head to head: Hugo and Jekyll, the veterans, versus Roq, the newcomer.

    Topics include:

    • Why WordPress core is usually fine, and the plugins are where the trouble is — over 10,000 plugin vulnerabilities found since 2025
    • What "recovery" means for a static site versus a CMS after a hack or defacement
    • Jekyll, Hugo, Roq and JBake compared, and why staying in Java matters (or doesn't)
    • How to extend Roq as a Java developer, from a small PR to writing your own plugin
    • What an actual WordPress-to-Roq migration looks like in practice
    • Where a CMS still earns its keep despite all of this


    Guests:

    Andy Damevin on LinkedIn - Principal Software Engineer at Red Hat, Quarkus core team, creator of code.quarkus.io and Roq

    Holly Cummins on LinkedIn - Senior Principal Software Engineer, Red Hat Quarkus team, led the quarkus.io migration from Jekyll to Roq


    Links:

    Migrate from WordPress to Roq
    Roq
    Hugo
    Full show notes


    Timestamps:
    00:00 Introduction of topic and guests
    03:29 Why WordPress is not the best choice for most sites
    04:36 Difference between CMS-driven websites and static websites
    07:02 Jekyll versus Roq and other systems
    11:04 How to extend Roq
    12:59 Moving from WordPress to Roq
    14:43 Pulling data with JBang or Roq from external sources into your publication process
    16:09 Why should I use Roq instead of Jekyll or Hugo?
    24:33 Static websites can be created with a small team and are much cheaper (or even free) to host
    26:52 How many WordPress websites have a backup to recover after getting hacked? And the advantage of having your content sources on Git.
    33:04 Is there still a use case for WordPress-like systems?
    37:09 Conclusions

    Exibir mais Exibir menos
    38 minutos
  • Java 27 in Practice: Smaller Heaps, Smarter Defaults, and Valhalla on the Horizon (#101)
    Sep 12 2026

    Episode 101 of the Foojay Podcast.

    JDK 27 arrives on 15 September 2026 without finalising a single new piece of language syntax. It is still worth the upgrade: object headers shrink from 64 bits to 32, which the JEP measures at 22% less heap and 8% less CPU on SPECjbb2015, and G1 becomes the default garbage collector on every machine. Both changes live inside the JVM, so an application you compiled years ago picks them up with no code change at all.

    Simon Ritter, Deputy CTO at Azul and Java Champion, takes us through all nine JEPs in the release, explains why a non-LTS version is still worth testing against, and makes the point that "long-term support" describes the binary you download rather than anything in OpenJDK itself. We also cover the move from quarterly to monthly security updates that started in August 2026, and then look ahead to March 2027, when Project Valhalla reaches its first preview after roughly twelve years of work.

    Topics include:

    • Compact object headers by default, and what 22% less heap actually buys you in production
    • Post-quantum key exchange in TLS 1.3, and the harvest-now-decrypt-later attack it defends against
    • JFR redaction: keeping access tokens and passwords out of flight recordings you share
    • Structured concurrency in its seventh preview, and why an evolving API stays in preview
    • The Vector API's twelfth incubation, and what it is waiting for
    • Value Objects in Java 28: a new value keyword, 179,000 lines, 1,800 files, and why it will not be final in JDK 29
    • Whether a Simple JSON API in the JDK will survive its previews, or go the way of string templates


    Guest: Simon Ritter
    Deputy CTO at Azul, Java Champion
    Simon on LinkedIn
    Simon on Foojay

    Links:
    Full show notes, with every JEP linked
    JDK 27
    What CSPUs Mean for Your Release Pipeline
    What to Know About Garbage Collection as a Java Developer!
    Project Valhalla

    Timestamps:
    00:00 Introduction of the topic and guest
    01:27 How long Simon has been doing Java
    01:54 Why release 27 is important, even when not being a Long Term Support release
    04:55 Quarterly and monthly security updates between new version releases
    08:07 Which JVM versions are most used in companies
    09:23 JEP 534: Compact Object Headers by Default
    14:51 JEP 523: Make G1 the Default Garbage Collector in All Environments
    18:59 JEP 527: Post-Quantum Hybrid Key Exchange for TLS 1.3
    22:55 JEP 538: PEM Encodings of Cryptographic Objects (Third Preview)
    25:35 JEP 536: JFR In-Process Data Redaction
    28:02 JEP 531: Lazy Constants (Third Preview)
    29:55 JEP 532: Primitive Types in Patterns, instanceof, and switch (Fifth Preview)
    33:13 JEP 533: Structured Concurrency (Seventh Preview)
    38:21 JEP 537: Vector API (Twelfth Incubator)
    40:28 Looking forward to Java 28 and Project Valhalla
    42:31 JEP 401: Value Objects and JEP 539: Strict Field Initialization
    47:36 Can we expect this to be finalized in Java 29?
    48:26 LTS releases every 1, 2, or 3 years?
    49:55 JEP 541: Deprecate macOS/x64
    51:53 JEP 540: Simple JSON API (Incubator)
    55:30 Conclusion, what to remember from this release

    Exibir mais Exibir menos
    58 minutos
  • Foojay Podcast #100: Java Podcasters on Why They Started, What Broke, and What They Learned (#100)
    Jul 11 2026

    Episode 100 of the Foojay Podcast. No grand plan. It just happened.

    To mark the milestone, Frank turned the microphone around and invited other podcasters: Adam Bien (airhacks.fm), Jennifer Reif (Breaktime Tech Talks), Kadi McKean and Steve Pool (10xInsights), and Oumaima Zerouali (JCast). Same questions for each: why did you start, what broke, and what did you learn?

    Along the way: why a no-prep podcast works when you have 20 years of experience, the difference between writing a blog and recording a podcast, burnout from editing, AI tools that changed someone's voice into Batman, and why a Dutch Java podcast about the human side of development got its first episode from a calendar invite that became a recording.


    Guests:

    • Adam Bien — airhacks.fm
    • Jennifer Reif — Breaktime Tech Talks
    • Kadi McKean and Steve Pool — 10xInsights
    • Oumaima Zerouali — JCast

    Links:

    • airhacks.fm on Spotify
    • Breaktime Tech Talks on Spotify
    • 10xInsights | 10xInsights on Spotify
    • JCast
    • Foojay Podcast #67: Writing a book. Does it make you rich and famous?
    • Foojay Podcast #71: 30 Years of Java with James Gosling
    • Foojay Podcast #99: Testing the Untestable: LLM Security for Java Developers with Tiberius
    • Frank on JCast
    • Other podcasts mentioned:
    • Spring Documentary


    Content:

    00:00 Introduction

    01:00 Adam Bien (airhacks.fm)

    12:52 Jennifer Reif (Breaktime Tech Talks)

    26:25 Kadi McKean and Steve Pool (10xInsights)

    38:43 Quote by James Gosling

    39:46 Oumaima Zerouali (JCast)

    48:01 Conclusion


    Hosted by Frank Delporte | foojay.io

    Exibir mais Exibir menos
    50 minutos
  • Testing the Untestable: LLM Security for Java Developers with Tiberius (#99)
    Jun 20 2026

    Your Java AI application is live in production. But have you tested whether it can be jailbroken, manipulated into revealing its system prompt, or tricked into printing content it should never output?

    In this episode, Iryna Dohndorf, Software Engineer at Karakun Group and creator of Tiberius, explains how to bring security testing to LLM-powered Java applications. We cover why traditional unit tests break down with non-deterministic systems, how the Scan-Fixture-Validate workflow works, what buff mutation testing is, and why even well-trained models can be cracked with something as simple as the grandmother attack.

    Topics include:

    • Why LLM non-determinism breaks the classic input/output test model
    • The Scan-Fixture-Validate principle and sharing test artifacts across teams
    • Prompt injection, jailbreaks, and emotional manipulation attacks
    • Buff mutation: testing linguistic surface coverage
    • Probabilistic security contracts and multi-trial scans
    • Fingerprinting and why your model choice should not be detectable
    • LLM as a judge: using a second model as a guardrail
    • Getting started with Tiberius in Spring Boot and LangChain4j

    Guest
    Iryna Dohndorf - Software Engineer at Karakun Group
    LinkedIn

    Links
    Article on Foojay
    Tiberius on GitHub
    Security Testing Guide

    Timestamps
    00:00 Introduction of topic and guest
    01:05 The problem Tiberius wants to solve
    06:39 How "traditional" unit tests don't work for LLM integrations
    10:23 Scan-Fixture-Validate principle and sharing artifacts
    15:15 Using different skills, for example, the grandmother skill
    17:33 Testing for required versus forbidden bias
    19:35 The probes across nine attack categories used by Tiberius
    20:44 Buff mutation testing
    26:55 Using Tiberius in your pipelines and when to fail
    29:35 Using multi-trial scans
    31:14 Fingerprinting: which model you use, should not be detectable
    32:55 Combining multiple models, model as a judge
    34:41 Sharing JSON models to improve tests
    36:05 How to get started with Tiberius in Spring and with LangChain4j
    36:41 Quarkus not supported yet, plans for the future
    39:07 Conclusions and a call out to everyone to become a Foojay author

    Exibir mais Exibir menos
    42 minutos
  • The End of JNI Pain: How WebAssembly Is Quietly Replacing Native Libraries in Java (#98)
    Jun 13 2026

    WebAssembly is already running inside Java applications, but most developers just don't know it yet.

    In this episode, Andrea Peruffo walks us through how WebAssembly is becoming the modern, safe alternative to JNI. Run Rust, C, and other native libraries directly on the JVM, without the crash risks, per-platform packaging headaches, or the observability blackhole that JNI creates.

    From JRuby's Prism parser to SQLite and full Postgres running as pure Java bytecode, the use cases are real. And the project making it possible, Endive, under the Bytecode Alliance, is open and ready to explore.

    Guest

    Andrea Peruffo

    • GitHub: https://github.com/andreaTP/
    • LinkedIn: https://www.linkedin.com/in/andrea-peruffo-32269178/
    • Bluesky: https://bsky.app/profile/andreatp.bsky.social

    Links


    • A New Generation of Java Libraries: Wasm Becomes the Implementation Detail

    • Chicory on GitHub

    • Endive on GitHub

    • Endive documentation

    • Bytecode Alliance

    • OpenJDK Project Detroit

    Timestamps
    00:00 Introduction of topic and guests
    00:56 What is WebAssembly?
    03:35 Comparing the performance with JavaScript
    05:45 JRuby already uses WebAssembly
    09:04 JNI versus FFM API versus WebAssembly
    13:58 Other Java-related tools that use WebAssembly
    17:56 History of the Chicory and Endive projects to bring WebAssembly to Java
    21:03 Projects of the Bytecode Alliance
    22:02 The Endive project as the glue to bring WebAssembly tools to Java
    23:30 Integration of the Redline compiler
    28:59 Why this is the perfect solution to modernize existing Java applications
    31:18 Is this approach performant?
    32:24 What future changes in Java and the JVM will make this even better
    35:04 How Endive can be used in AI development
    37:28 What to expect in Endive
    41:29 Conclusions

    Exibir mais Exibir menos
    44 minutos