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
sign_update pem invalid macOS High Sierra #1180
Comments
I'm guessing the fact the old private key and the one in the example project don't work (And the keychain doesn't like these files either) suggest this is an issue with macOS high Sierra, and more specifically libressl |
We've got multiple reports about signatures failing. There's certainly something flaky about it. My personal key does work, so it may be a bug or broken support for some key size or other property of the key. Sorry for the annoyance it causes. Long term we'll be moving to more modern signature scheme. I'm not sure what do about it short term, other than hope Apple fixes it :( |
Sad times It's no worries, I ended up looking at the bash script and manage to get a signature in the end 👍 |
Need to replace the DSA key with one generated on 10.12 as it breaks. For more: sparkle-project/Sparkle#1180
I have recently been trying to update a Mac app which I haven't been working on for a while. When I try and run
sign_update
I get this error:I have tried the old private pem file I had, one newly generated using
generate_keys
and the one bundled with the example project. All of them throw this error in the console, and I also get an error when trying to open them inkeychain.app
.The text was updated successfully, but these errors were encountered: