Skip to content

gh-136134: Fallback to next auth method when CRAM-MD5 fails due to unsupported hash (e.g. FIPS) #136188

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.

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

bpo-136134: Clarify comment on handling unsupported hash in CRAM-MD5

ba5c991
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Closed

gh-136134: Fallback to next auth method when CRAM-MD5 fails due to unsupported hash (e.g. FIPS) #136188

bpo-136134: Clarify comment on handling unsupported hash in CRAM-MD5
ba5c991
Select commit
Loading
Failed to load commit list.
Change detection / Create context from changed files
succeeded Jul 2, 2025 in 12s