Skip to content

Conversation

@Bibo-Joshi
Copy link
Member

See #2372

I propose to leave #2372 open and give the cryptography time to figure out their plans for the future. As we need cryptography only for passports (and I've never met anyone acutally using those …) it's not a main security issue. Nevertheless I subscribed to the cryptography release channel to keep an eye on the changelog for security fixes.

If the situation is more clear in the future we can think about how we want to approach the issue.

Copy link
Member

tsnoam commented Feb 9, 2021

@Bibo-Joshi In asyncio branch I've been using httpx which is using cryptography

Copy link
Member Author

@tsnoam Only for the tests apparently: https://github.com/encode/httpx/blob/master/requirements.txt#L19

Copy link
Member

tsnoam commented Feb 10, 2021

@Bibo-Joshi Interesting. How do they perform https communications then?

Need to check.

Copy link
Member

tsnoam commented Feb 10, 2021

uh. using the standard ssl.
https://github.com/encode/httpx/blob/master/httpx/_types.py

ok.

Copy link
Member Author

@tsnoam Acutally the more convincing proof for "they only use it for tests" is here 😁

@Bibo-Joshi
Copy link
Member Author

Closing in favor of #2386

@Bibo-Joshi Bibo-Joshi closed this Feb 13, 2021
@Bibo-Joshi Bibo-Joshi deleted the crypto-dep branch February 13, 2021 10:49
@github-actions github-actions bot locked and limited conversation to collaborators Feb 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants