Skip to content
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

[Tracking][security] cryptography is pinned < 3.4 due to rust; needs resolving over time #421

Open
ajkavanagh opened this issue Feb 9, 2021 · 1 comment
Open

[Tracking][security] cryptography is pinned < 3.4 due to rust; needs resolving over time #421

ajkavanagh opened this issue Feb 9, 2021 · 1 comment

Comments

@ajkavanagh
Copy link
Collaborator

Recent (>=3.4) versions of python cryptography now ship with rust code for some of the operations. This breaks in some scenarios (e.g. openstack-charmers/zaza-openstack-tests#369).

However, we do not want to remain pinned for long as it is a security related module. The main issue is rust builds for charms.reactive charms which needs a build for each platform. Or we need to NOT have the rust code.

Related: #420 pins to <3.4 in zaza.
@lourot
Copy link
Contributor

lourot commented Feb 10, 2021

Temporary pinning here as well:

coreycb pushed a commit to coreycb/zaza that referenced this issue Oct 17, 2023
@dshcherb
Merge pull request openstack-charmers#421 from openstack-charmers/lou…
d04befa 
…rot/bug/1895636

Make test_manila_share more robust
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ajkavanagh @lourot