jetty/jetty.project

Easier access to invalid client certificates

Open

#6,067 创建于 2021年3月17日

在 GitHub 查看
 (5 评论) (0 反应) (0 负责人)Java (3,701 star) (1,913 fork)batch import
Help Wanted

描述

Jetty version 10.0.x

Description During the TLS handshake, in case of needClientAuth, the client may send an invalid (e.g. expired) certificate. The validation checks are performed by the TrustManager and if they fail there is no way to access the expired client certificate, for example in SslHandshakeListener.handshakeFailed(), as it is not exposed via SSLSession.getPeerCertificate(), etc.

The only option would be to wrap the TrustManager, but that requires subclassing SslContextFactory.Server and overriding getTrustManager(), whose signature is likely to change in light of #6054.

Would be great to have a more stable way to provide hooks into the TrustManager in a simpler way.

贡献者指南

技术栈
java
领域
backendsecurity
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
JavaTLS/SSL basicsJetty SslContextFactory
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate how Jetty's SslContextFactory.Server creates TrustManager instances and where client certificate validation occurs. Look at SslHandshakeListener.handshakeFailed() and SSLSession to understand current limitations. The goal is to expose invalid client certificates in the handshake failure callback, possibly by creating a wrapper trust manager or modifying the SslContextFactory API. Examine upstream issue #6054 for potential API changes.