8000 IMAP/Submission: don't hard-code SCRAM-SHA-256 authentication mechanism, make it configurable · Issue #5 · mjl-/gopherwatch · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

IMAP/Submission: don't hard-code SCRAM-SHA-256 authentication mechanism, make it configurable #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
mjl- opened this issue Feb 25, 2024 · 0 comments
Open

IMAP/Submission: don't hard-code SCRAM-SHA-256 authentication mechanism, make it configurable #5

mjl- opened this issue Feb 25, 2024 · 0 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@mjl-
Copy link
Owner
mjl- commented Feb 25, 2024

We now always do SCRAM-SHA-256 when submitting email, and also when connecting to IMAP.

Not all mail servers support this. We should make it configurable (but always require that admins specify a mechanism, we don't want downgrade attacks).

Mox has some (test) code that handles selecting different authentication mechanisms, can probably borrow from that.

64A3
@mjl- mjl- added help wanted Extra attention is needed good first issue Good for newcomers labels Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mjl-
0