-
Notifications
You must be signed in to change notification settings - Fork 308
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
Unable to upload package when FIPS is enabled on workstation #775
Comments
That's interesting as we have a test for FIPS Lines 241 to 250 in b4a196e
That said, this is an interaction with Nexus where that test was almost certainly written against PyPI. We can't test against Nexus and PyPI would seem to accept this without issue. We could exclude |
Once again, we have to deal with third-party package repositories doing their own thing and users needing this to just work. Those repositories combined with FIPS mean that we will need to send the information we actually have and only that when it comes to digests. Closes gh-775
Once again, we have to deal with third-party package repositories doing their own thing and users needing this to just work. Those repositories combined with FIPS mean that we will need to send the information we actually have and only that when it comes to digests. Closes gh-775
* Send only the digests we have from PackageFile Once again, we have to deal with third-party package repositories doing their own thing and users needing this to just work. Those repositories combined with FIPS mean that we will need to send the information we actually have and only that when it comes to digests. Closes gh-775 * Update function and comments for clarity Let's be clearer about some of the bizarre logic we use to support repositories other than PyPI and distributions using FIPS Co-authored-by: Brian Rutledge <[email protected]> Co-authored-by: Brian Rutledge <[email protected]>
Released in https://pypi.org/project/twine/3.4.2/ |
Your Environment
Thank you for taking the time to report an issue.
To more efficiently resolve this issue, we'd like to know some basic information about your system and setup.
Your operating system: CentOS 7.9
Version of python you are running: Python 3.6.8
How did you install twine? Did you use your operating system's package manager or pip or something else? Installed via pip in a virtualenv
Version of twine you have installed (include complete output of): twine version 3.4.1 (importlib_metadata: 4.6.1, pkginfo: 1.7.1, requests: 2.25.1, requests-toolbelt: 0.9.1, tqdm: 4.61.2)
Which package repository are you targeting? Private Nexus PyPi repository
The Issue
Our development workstations were recently "upgraded" to enable FIPS. twine successfully creates the package, however the package fails to upload because a blank md5_digest is being sent in the HTTP payload. When this value is left in, our Nexus repo is responding with something like:
The part after "expected" is the empty
md5_digest
from the HTTP payload.I manually edited
package.py
, removedmd5_digest
from themetadata_dictionary
return value, and the file uploaded successfully.Steps to Reproduce
Unfortunately I'm not able to test this using the "test" PyPi server as the workstation I'm using is on a private lab/LAN. However, I have to assume this would function the same when trying to publish to there.
twine upload --repository-url=https://internal.server/repository/repo/ dist/*
The text was updated successfully, but these errors were encountered: