-
Notifications
You must be signed in to change notification settings - Fork 41
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
Not able to use JSS_importer after logjam updates #42
Comments
Yep! That's the issue I'm literally working on right now. The code in the testing branch reflects my proposed changes. I'd post a "beta" egg/wheel but figuring out how to do that might take more time than just making the fixes. If you dm me on twitter I can send you the dropbox link for the current testing version if you want to be a tester. |
I'm testing it in place of my existing pip installation :) I did have to install request and ndg-httpsclient, and distutils/version.py didn't like the 'rc2' in the init.py, but once I got rid of that everything (appears to be) running fine. |
Well, in that case, proceed. According to pypi.python.org, the recommended naming scheme is as above (the rc2). But obviously distutils doesn't like that. This is the first time I've released a testing version, so I'll have to look more closely at that. In the meantime, as I'm sure you discovered, just drop the rc2 from the version in jss/init.py and it will work fine. |
Fixed in 1.2.1 |
I recently had a JAMF health checkup and we updated the ciphers for Tomcat to get around the Logjam problem (see https://jamfnation.jamfsoftware.com/article.html?id=384), but now I'm not able to push any JSS recipes!
Using the builtin openssl to view the cert doesn't work, but using an updated one from Macports does.
I've disabled SSL_VERIFY and otherwise done every suggestion I've been able to find. I also tried updating the openssl on my autopkg'ing machine but it didn't seem to work, even after a reboot.
The text was updated successfully, but these errors were encountered: