HTTPS certificate validation disabled
An AI assistant produced this Java method to call a partner's HTTPS webhook. It connects successfully and the integration test passes against the partner's real endpoint. Review it before merge.
Implement
certificate_is_trusted(cert_subject: str, cert_issuer: str, requested_host: str, trusted_issuers: list[str]) → boolExamples
in
["api.example.com","Real CA","api.example.com",["Real CA"]]outtruein
["api.example.com","Rogue CA","api.example.com",["Real CA"]]outfalsein
["*.example.com","Real CA","api.example.com",["Other CA","Real CA"]]outtrueWhat a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 16 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.