Skip to content
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

Signing issues on OSX #826

Closed
samoht opened this issue Jul 11, 2016 · 5 comments
Closed

Signing issues on OSX #826

samoht opened this issue Jul 11, 2016 · 5 comments

Comments

@samoht
Copy link

samoht commented Jul 11, 2016

Due to golang/go#11887 the notary binary, when signed, will not run on OSX. We currently workaround the issue by rebuilding the application with striped dwarf symbols:

djs55@31e4b19

Would be great to have a proper solution integrated upstream.

/cc @justincormack and @djs55

@endophage
Copy link
Contributor

endophage commented Jul 11, 2016

Just curious, which version of Go are you using? That linked issue seems to indicate the solution you're using ceased working on 1.5.2 and 1.6.

Definitely want to work out a good way to fix this. I was talking to the Yubico guys about how we might go about dropping to cgo requirement (we'd have to write a Go integration from the ground up, probably against PIV rather than PKCS11), but I haven't had any time to look into it.

@justincormack
Copy link
Contributor

Fairly sure we are compiling with 1.6; the solution still works, that is what we ship with docker for mac.

I don't think always stripping the dwarf is a problem for other platforms, can do a PR for that.

A non cgo version would be nice, but it is quite a bit of work I would imagine...

@dmp42
Copy link
Contributor

dmp42 commented Jul 12, 2016

Doesn't the last comment on that go ticket suggest the latest clang version fixes the issue? (clang-703.0.29)

@justincormack
Copy link
Contributor

The comments on the issues don't correspond much to our experience, but I will test again on a fully updated system.

@endophage
Copy link
Contributor

Closing due to inactivity and afaik, fixes and workaround in place.

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

No branches or pull requests

4 participants