Skip to content

🔒 Cancel SASL authentication after client-side exceptions #310

Open

Description

@nevans

From RFC9051 6.2.2

If the client wishes to cancel an authentication exchange, it issues a line consisting of a single "*". If the server receives such a response, or if it receives an invalid base64 string (e.g., characters outside the base64 alphabet or non-terminal "="), it MUST reject the AUTHENTICATE command by sending a tagged BAD response.

Currently, exceptions should cause the connection to be dropped, but that's too severe a reaction.

When authentication is canceled, the original exception should be the #cause of any resulting BAD exception. This way it will be captured by automated error reporting.

Activity

  1. added
    SASL 🔒Authentication and authentication mechanisms
    on Oct 3, 2024
  2. added this to the v0.6 milestone on Oct 14, 2024
  3. added
    IMAP4rev2Requirement for IMAP4rev2, RFC9051
    IMAP4rev1Requirement for IMAP4rev1, RFC3501
    on Oct 14, 2024
  4. modified the milestones: v0.6, v1.0 on Dec 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    IMAP4rev1Requirement for IMAP4rev1, RFC3501IMAP4rev2Requirement for IMAP4rev2, RFC9051SASL 🔒Authentication and authentication mechanisms

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions