-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Openssl version not detected in current oscrypto version (pypi) #78
Comments
Having a bugfix release would be much appreciated we are seeing this issue on AWS Ubuntu AMIs after issuing system updates, I can imagine that there are a few less than happy AI developers out there struggling to work their way back to this issue. |
We are seeing the same issue too. The OpenSSL version we are using happens to be 3.0.10. Would really appreciate it to have a new release. Thanks! |
The same |
@wbond Any chance you can look into this issue? |
+1 for a bugfix release v1.3.1 |
+1 for a new release, this is a dependency of snowflake-connector-python, so I imagine many folks are impacted and pinning their OpenSSL version. Thanks for your time and care, we appreciate it! |
I manually edited the file and changed the last |
Any update on when this will be released? |
No, this is a free-time project for me. The commit is there, so it is certainly possible to use most Python packaging tools to grab the sha of the commit. |
For those too impatient, like myself... in my pyproject.toml I added in:
And now we're all systems go. Thanks for taking the time to create this @wbond ! |
Thanks for the quick response, and appreciate the work you put into the package @wbond ! |
@connor-lough For projects that don't use pyproject.toml, is there a way you can do this via the requirements.txt file? |
This is the line I added to my requirements.txt: I also had to add "git" to my Dockerfile, because I was not installing git before: |
Thank you! |
We are facing the same issue. Using |
@vermavikrant Yes, the problem is due to a conflict with the
Or
|
I've spent most of the day updating our internal applications that use snowflake-connector. My fixes follow along the lines of what has been suggested, above. If you're using Docker to build your app, you can include a pip install of the ocscrypo package prior to snowflake-connector, and it'll assume the dependency has already been met:
If you need to embed it into a requirements.txt file, you can add the following line:
|
If installing via setuptools.setup, then the following line should work @mwisconsin wondering why your commit hash is different? Was the fix not in d5f3437 ? |
@vermavikrant I picked the latest just in case the recent commits fixed other problems I might encounter in the upcoming weeks before a release happens. |
Installed it directly with |
Snowflake which is a $50,000,000,000 company should be paying you something, since their tool requires your good graces. IMO. |
Unsurprisingly, Snowflake chose to move away from this lib instead: https://github.com/snowflakedb/snowflake-connector-python/blob/main/DESCRIPTION.md |
@wbond Is there anything that a willing contributor can do to facilitate/expedite publishing a patch release to PyPI? I work for a company that is currently affected by this issue. I well am within my rights here to dedicate some work time to helping with a PyPI release that includes this bugfix. I can't actually benefit from Snowflake dropping your project as a dependency, because I'm stuck on an older version of their library. So you can consider me a fully captive audience. It seems like I need to do the following:
I imagine I need both Git committer access in this repo, and contributor access to the Just let me know what I can do to help get this published. Edit: It seems like there have been a lot of changes since v1.3.0 was published, and it would be a lot of work for a new contributor to sort through the commit history in order to document all of it. Would it be acceptable to cherry-pick just this one patch (+ some minimal subset of related commits, if necessary) into a separate branch to create the release? If so, what's your recommended process for that? I assume you're not interested in rebasing all of |
PSA: snowflake-connector-python 3.4.0 has been released: https://github.com/snowflakedb/snowflake-connector-python/releases/tag/v3.4.0. |
Fixed a bug in oscrypto where the regex would fail to recognize the right version of SSL due to insufficient check on multiple digits. However the owner of the repo does not plan to make a new release soon due to time constraints. See -> wbond/oscrypto#78 This can be fixed by using a specific version from git pointing to the right commit. Hence this change in the pyproject.toml file.
Signed-off-by: John Andersen <johnandersenpdx@gmail.com>
Signed-off-by: John Andersen <johnandersenpdx@gmail.com>
Many dependents of minikerberos don't need `PKINIT`, so it makes sense to import `oscrypt` only when needed. Especially because `oscrypt<=1.3.0` does not work when `openssl>=3.0.10`. See: wbond/oscrypto#78
Oscrypto has not yet releasedawith fix to this wbond/oscrypto#78 so we need to lock the oscrypto version until the fix is released. PR #3958
Oscrypto has not yet releasedawith fix to this wbond/oscrypto#78 so we need to lock the oscrypto version until the fix is released. PR #3958
any chance for a new release so that installations from pypi will include fixes such as this? |
As the developer of cryptolyzer (free software), which depends on oscrypto indirectly (certvalidator), I would highly appreciate it if you could release the fix for the issue. |
I'm running into this issue on an ubuntu:latest docker container running on an ARM cpu. in my case it was fixed with:
Is there something I can help with for there to be a new release version on pip? #81 |
@wbond Are there any news when the next release is planned? |
Same problem with @wbond is there anything we can help make this pypi release happen? |
Hi,
first of all thank you for your work!
We are currently encountering the Error:
oscrypto.errors.LibraryNotFoundError: Error detecting the version of libcrypto
See: https://github.com/mpgn/CrackMapExec/issues/108
I saw you already fixed that in d5f3437, but as this is not released to pypi our Tool does not fully work. Would it be possible to release a bug-fix version to pypi?
The text was updated successfully, but these errors were encountered: