Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • mutt mutt
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mutt Project
  • muttmutt
  • Issues
  • #245
Closed
Open
Created Jun 05, 2020 by Kevin J. McCarthy@kevin8t8Maintainer

GnuTLS continuing after rejecting certificate?

henk on irc writes:

02:00 <      henk> Hi, #mst-374: I’m running mutt 1.10.1-2.1 on debian stable 
                   and use it to connect to an ssl-enabled imap-server. One of 
                   the certificates in the certificate-chain the server sends 
                   is expired and mutt displays "WARNING: Server certificate 
                   has expired" and gives me the options "(r)eject, accept 
                   (o)nce". When I press 'r', it still continues to connect 
                   and asks for my password. The behaviour is exactly the same
02:00 <      henk> when I press 'o'. I would have expected it to stop 
                   connecting when I press 'r'. Does anyone know the rationale 
                   behind that? It feels like a bug to me but maybe I miss 
                   something.
Assignee
Assign to
Time tracking