How do I add a trusted certificate authority to packer

[Stanford Guillory]

Hello,

     I am having issues just getting the simplest packer commands running on OS X. For instance, logging on,  "packer --version" returns:

Packer v0.7.1

2014/10/23 08:07:39 ui: Packer v0.7.1

2014/10/23 08:07:39 [ERR] Checkpoint error: Get https://checkpoint-api.hashicorp.com/v1/check/packer?arch=amd64&os=darwin&signature=33a9e121-884f-e607-ca6b-df841e6fd837&version=0.7.1: x509: certificate signed by unknown authority

This is because my firm is using a product to insert their self-signed cert in the middle of all SSL requests so they can examine traffic. With other tools, i.e. npm, wget, etc. we get around this in by adding that cert as a trusted authority. The cert is in my keychain on my mac book. But some tools, i.e. firefox, use a different cert store and it appears packer is one of those. How do I had a cert to the store packer is using on OS X?

Thanks,

Stanford S. Guillory

Solutions Architect

Southwest Airlines Co.

 

[Stanford Guillory]

Packer 0.7.2 was released today and seems to fix the issue for me. 

[BG]

How did you get around this problem? How does that version keep you from getting the 509 error?

[Ethan S.]

For the most part you can safely ignore this error, this is simply a usage tracking mechanism, with their vagrant tool it's also used for licensing so it becomes more troublesome there. If your enterprise is intercepting the certificate and rewriting it you will need to accept your organization's rewritten certificate, this is probably easiest to do by attempting to visit the URL and using your browser to save/export your organizations certificate, then use the OSX keychain to import it system wide.