jodersky/sbt-gpg

Need key without passphrase protection

Closed this issue · 6 comments

seahrh commented

I took awhile to get sbt publish to work on Travis after following the steps in this section https://github.com/jodersky/sbt-gpg#securely-publishing-in-travis-and-other-ci

What I didn't realise at the time is that my key is still passphrase protected. I was puzzled when the interactive passphrase prompt threw off my travis build.

The solution is to not password-protect the CI signing key and instead encrypt it explicitly using openssl. To start with, ...

Probably it would be clearer if we emphasize the first step is to create a new key without passphrase protection.

If you like, I can do a PR on README to clarify the above.

djspiewak commented

I think it would be worth clarifying. To be clear though, you should be using a new key for Travis anyway (not your personal GPG key; never your personal GPG key), so when I wrote those instructions I was expecting people were generating things in the moment and would be caught by that sentence.

jodersky commented

Sounds good! Please open a PR if you have any clarifications you'd like to add

seahrh commented

OK, I need permission to push the branch.

$ git push --set-upstream origin i11
remote: Permission to jodersky/sbt-gpg.git denied to seahrh.
fatal: unable to access 'https://github.com/jodersky/sbt-gpg.git/': The requested URL returned error: 403
jodersky commented
seahrh commented

Got it, let me create PR from my own fork

jodersky commented

Fixed in #12