2 ms·
The title of this post is wildly misleading: Go’s behavior is correct here. But even if it wasn’t, failing closed isn’t generally a way one fools a X.509 path v
by woodruffw 5mo ago
The title of this post is wildly misleading: Go’s behavior is correct here. But even if it wasn’t, failing closed isn’t generally a way one fools a X.509 path validator.
Source: having had the displeasure of implementing an RFC 5280 and CABF-conforming path validator.