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.

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

Build fails with Python 3.13 and python3-cryptography 43.0.0 #228

Open
bkmgit opened this issue Nov 3, 2024 · 10 comments
Open

Build fails with Python 3.13 and python3-cryptography 43.0.0 #228

bkmgit opened this issue Nov 3, 2024 · 10 comments

Comments

@bkmgit
Copy link
Contributor

bkmgit commented Nov 3, 2024

Which version of python are you using?

3.13

What operating system and version of operating system are you using?

Fedora Rawhide (42)

What version of sewer are you using?

Current release

What did you do? (be as detailed as you can)

Tried to import installed package

What did you expect to see/happen/not happen?

Expected import to work ok

What did you actually see/happen?

AttributeError: module 'cryptography.hazmat.backends.openssl' has no attribute 'rsa'

Paste here the log output generated by sewer, if any. Please remember to remove any sensitive items from the log before pasting here.

If you can, run sewer with loglevel set to debug; eg sewer --loglevel DEBUG

Alternatively if you want to conribute to this repo, answer this questions instead in your issue:

What is it that you would like to propose to add/remove/change?

It seems a private API has been used:
pyca/cryptography#11147

Why do you want to add/remove/change that?

How do you want to go about adding/removing/changing that?

@komuw
Copy link
Owner

komuw commented Nov 3, 2024 via email

@bkmgit
Copy link
Contributor Author

bkmgit commented Nov 9, 2024

Thanks.

@bkmgit bkmgit closed this as completed Nov 9, 2024
@mmaney
Copy link
Collaborator

mmaney commented Nov 12, 2024

@bkmgit Although I haven't done much to the codebase since 2020, I still use sewer, so I have some interest in seeing this fixed before cryptography's changes hit me. I've taken a look at it and it seems like it will be a pretty easy fix, but I need a tester who's using a more recent cryptography package. Are you still interested in sewer or have you moved on? And if the latter, where to? :-)

@mmaney mmaney reopened this Nov 12, 2024
@bkmgit
Copy link
Contributor Author

bkmgit commented Nov 12, 2024

@mmaney Ok, will make a pull request to fix these issues. If you can test, that would be great.

@mmaney
Copy link
Collaborator

mmaney commented Nov 12, 2024 via email

@mmaney
Copy link
Collaborator

mmaney commented Nov 12, 2024 via email

@bkmgit
Copy link
Contributor Author

bkmgit commented Nov 12, 2024

Ok, will update the testing pipelines.

@mmaney
Copy link
Collaborator

mmaney commented Nov 13, 2024

@bkmgit Ignore the patch, I just realized that the local repo I was working in was NOT a clean copy master. I'll rework it in a clean copy after dinner...

@mmaney
Copy link
Collaborator

mmaney commented Nov 13, 2024

IT'S WORSE THAN THAT. Some of the work since 0.8.4 appears to be incomplete, quite possibly works only because of luck? At this point, I am no longer confident that it actually does work. All the "0.8.5" stuff OUGHT to have been sequestered in a dev branch, I think. The refactoring of crypto.py, in particular, actually makes it MORE entwined with those private bits that we need to disengage from. :-(

Telling: the installed copy I still use to update certs is 0.8.4 from pypi. And 0.8.4 was the base that the above patch applies on. Right, let's work on crypto-cleanup branch which has my (still untested... oh, need to fix the CI stuff, don't I?) changes. Crossing fingers...

@bkmgit
Copy link
Contributor Author

bkmgit commented Nov 22, 2024

Will examine code. Added basic pipeline
#229

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants