spaces-integration-proton-tls
default.ciChecks.x86_64-linux.spaces-integration-proton-tls
· build #4
· raw
1PASS: serving cert carries Basic Constraints CA:TRUE (mimics Proton Bridge)2=== generate himalaya.toml + msmtprc via integration_proton._build_config ===3GENERATED himalaya.toml + msmtprc4=== generated config: integration pins backend.encryption.cert + tls_trust_file ===5PASS: generated himalaya config pins backend.encryption.cert at the Bridge cert6PASS: generated msmtprc carries tls_trust_file at the Bridge cert7=== IMAP positive: himalaya trusts the CA:TRUE cert via the integration's pin ===8FAIL: himalaya did NOT complete TLS (stub: IMAP_LISTEN 14143)9PASS: no CaUsedAsEndEntity / cert error from himalaya when pinned10=== IMAP negative: strip the integration's pin -> default verifier rejects CA:TRUE ===11FAIL: expected a TLS rejection without pin, got: Suggestions: - Run with --log-level to enable more verbose logs 12=== SMTP positive: msmtp trusts the CA:TRUE cert via the integration's tls_trust_file ===13PASS: msmtp trusted the CA:TRUE cert via tls_trust_file (no cert error)14=== SMTP negative: point trust_file at an unrelated cert -> msmtp must reject ===15PASS: msmtp rejected the mismatched cert (trust_file is enforced)1617RESULT: FAILURES