Notarization always failed (JWT error)

[TheOnlyJoey]

What happened:
`quill sign-and-notarize --p12 mycert.p12 MyApp.component/Contents/MacOS/MyApp

✔ Signed binary MyApp.component/Contents/MacOS/MyApp
notarization failed: unable to parse EC private key for JWT: invalid key: Key must be a PEM encoded PKCS1 or PKCS8`

What you expected to happen:
Seems to be an internal error, no clue how to debug

How to reproduce it (as minimally and precisely as possible):
Export Developer Id cert and private key for signing as p12 on mac, run command quill sign-and-notarize --p12 mycert.p12

Anything else we need to know?:

Environment:

• Output of version command: 0.5.1
• OS (e.g: cat /etc/os-release or similar): Same result on Debian Trixie and macOS 14

[willmurphyscode]

Thanks for the report @TheOnlyJoey! If you run again with more logging, e.g. -vv, do you get anything more helpful?

[TheOnlyJoey]

i just realized that won't be possible, the moment i add -vv to --p12, it gives a message about needing a password, but it won't prompt for a password anymore.

[willmurphyscode]

Well that sounds like a bug we should work on. Thanks for giving it a try!

[TheOnlyJoey]

No problem! Trying to integrate quill into my CI/CD for vst/component signing so might run into a couple more exceptions throughout testing.

[willmurphyscode]

It might be helpful to you to look at how we use quill in our release, which is https://github.com/anchore/grype/blob/e64e1bac15c5438b3f03b19be972ddc9ce478ee1/.goreleaser.yaml#L46 called from https://github.com/anchore/grype/blob/e64e1bac15c5438b3f03b19be972ddc9ce478ee1/.github/workflows/release.yaml#L182

This use case is what we use quill for, so things that get too different from this use case (in terms of artifact type or signing method) might not be as well supported.