Skip to content
This repository has been archived by the owner on Jan 28, 2022. It is now read-only.

consider changing the signature source from an individual to CFF #21

Open
jbayer opened this issue Feb 21, 2018 · 1 comment
Open

consider changing the signature source from an individual to CFF #21

jbayer opened this issue Feb 21, 2018 · 1 comment

Comments

@jbayer
Copy link

jbayer commented Feb 21, 2018

right now the README states that files are signed by the @sclevine keybase.io. is there a better approach than using an individual in the future?

@sclevine
Copy link
Contributor

sclevine commented Feb 22, 2018

There's some discussion about this here. Bret has also reached out to me directly about signing the CF Local binaries with a trusted code signing certificate so that they can be used on locked-down Windows machines.

I should follow up with @chipchilders to see if the CFF could send me a hardware token with the same code signing certificate that's used by the CF CLI, or alternatively, if the CFF could purchase additional certificates for CLI plugin authors.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants