{"version":"2.1.307","anchor":"jvm-truststore-is-filtered-and-rebuilt-more-defensively","canonical_anchor":"jvm-truststore-is-filtered-and-rebuilt-more-defensively","heading":"Java certificate setup for remote sessions is more careful","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/jvm-truststore-is-filtered-and-rebuilt-more-defensively","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Java certificate setup for remote sessions is more careful\n\nClaude Code now filters the Java truststore, requires every needed certificate, and cleans up leftover files when setting it up for remote sessions\n\n**What**\n\nA truststore is the list of security certificates a Java program uses to decide which secure connections to trust. When Claude Code sets one up for Java programs in remote sessions, it now:\n\n- filters the system's own truststore, and reports \"could not filter the JVM truststore\" if that fails\n\n- requires every certificate the remote session needs to be present\n\n- cleans up leftover temporary files\n\n- retires a truststore that fails these checks\n\nBefore, it only checked that one certificate was present and then imported it.\n\n**Why**\n\nJava programs in remote sessions should hit fewer broken secure-connection setups.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}