spaces-integration-proton-tls
default.ciChecks.x86_64-linux.spaces-integration-proton-tls
· build #61
· raw
1tribuchet: building on gi-build-x86-022PASS: serving cert carries Basic Constraints CA:TRUE (mimics Proton Bridge)3=== generate himalaya.toml via integration_proton._build_config ===4GENERATED himalaya.toml5=== generated config: integration pins imap.tls.cert + smtp.tls.cert ===6PASS: generated himalaya config pins imap.tls.cert at the Bridge cert7PASS: generated himalaya config pins smtp.tls.cert at the Bridge cert8=== IMAP positive: himalaya trusts the CA:TRUE cert via the integration's pin ===9PASS: himalaya completed TLS against the CA:TRUE cert (integration pin works)10PASS: no CaUsedAsEndEntity / cert error from himalaya when pinned11=== IMAP negative: strip the integration's pin -> default verifier rejects CA:TRUE ===12PASS: without the pin himalaya rejects the CA:TRUE cert (the hazard is real)13=== SMTP positive: himalaya trusts the CA:TRUE cert via the integration's pin ===14PASS: himalaya trusted the CA:TRUE cert via smtp.tls.cert (no cert error)15=== SMTP negative: strip the integration's pin -> default verifier rejects CA:TRUE ===16PASS: without the pin himalaya rejects the CA:TRUE cert over SMTP1718RESULT: ALL-PASS