-
Notifications
You must be signed in to change notification settings - Fork 112
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
urllib3.util.ssl_ has no attribute DEFAULT_CIPHERS
#142
Comments
Reverting to the following library to an older version helped for me: |
Thanks! Although, I think it is important to properly set the cipher or have a reasonable default going forward, and I'm not sure what makes the most sense for this library/API. |
I encountered the same error (urllib3.util.ssl_ has no attribute DEFAULT_CIPHERS). Tried this and also downgrading urllib to 1.25.11 as suggested elsewhere, but now I get:
Any hints? |
I'm experiencing the same issue. |
The DEFAULT_CIPHERS issue looks like it has been fixed here: For those of you who have downgraded to openssl3 doesn't work... so I wrote a small Dockerfile to take care of getting a master token. After you have a master token, you can use other functionality with openssl3 without worrying about the BadAuthentication error. |
Closing since the issue is now resolved. |
Please make sure you've done the following before submitting your issue:
Additionally, please provide the following information:
Stack trace:
It looks like
urllib3
no longer defines this, which is used bygpsoauth
. Unclear what the cleanest way to repair / mediate this going forward is, as it seems we need to specify a cipher in order for google to permit logins. I manually modified thegpsoauth
package to put theDEFAULT_CIPHERS
back in but still got(BadAuthentication, None)
error.The text was updated successfully, but these errors were encountered: