spaces-integration-proton-tls
checks.x86_64-linux.spaces-integration-proton-tls
· build #170
· raw
1PASS: serving cert carries Basic Constraints CA:TRUE (mimics Proton Bridge)2=== generate himalaya.toml via integration_proton._build_config ===3GENERATED himalaya.toml4=== generated config: integration pins imap.tls.cert + smtp.tls.cert ===5PASS: generated himalaya config pins imap.tls.cert at the Bridge cert6PASS: generated himalaya config pins smtp.tls.cert at the Bridge cert7=== IMAP positive: himalaya trusts the CA:TRUE cert via the integration's pin ===8PASS: himalaya completed TLS against the CA:TRUE cert (integration pin works)9PASS: no CaUsedAsEndEntity / cert error from himalaya when pinned10=== IMAP negative: strip the integration's pin -> default verifier rejects CA:TRUE ===11PASS: without the pin himalaya rejects the CA:TRUE cert (the hazard is real)12=== SMTP positive: himalaya trusts the CA:TRUE cert via the integration's pin ===13PASS: himalaya trusted the CA:TRUE cert via smtp.tls.cert (no cert error)14=== SMTP negative: strip the integration's pin -> default verifier rejects CA:TRUE ===15PASS: without the pin himalaya rejects the CA:TRUE cert over SMTP1617RESULT: ALL-PASS