Foojay.io | Friends of OpenJDK and Java Programming Podcast Por Foojay.io | Java and Programming Community capa

Foojay.io | Friends of OpenJDK and Java Programming

Foojay.io | Friends of OpenJDK and Java Programming

De: Foojay.io | Java and Programming Community
Ouça grátis

Ofertas da temporada | R$ 0,99/mês por 3 meses

R$ 19,90/mês após 3 meses. Confira termos e condições
Sobre este título
Foojay.io is your go-to programming community podcast, connecting developers with the latest in Java, OpenJDK, JVM, and open source tools. We bring together Java professionals worldwide to share insights, tools, and news in the vibrant Java programming ecosystem.Foojay.io | Java and Programming Community Política e Governo
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
adbl_web_anon_alc_button_suppression_t1
Ainda não há avaliações