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.

Sign up for GitHub

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

Jump to bottom

How should we manage the Threema CA cert? #11

Open

willnix opened this issue Jan 4, 2017 · 1 comment

Labels

enhancement help wanted

Contributor

willnix commented Jan 4, 2017

The certificate is used in o3/blob.go and go-unirest/Requests.go and it would be nice to only have one instance of it, in case it changes.

this is just a reminder will add more thoughts later

willnix added enhancement help wanted labels

Member

cryptix commented Jan 5, 2017

I'd add a GetPinnedTLSCert() []byte to o3ma/o3 and use that here and in the go-unirest fork.

Ideally this should also reduce the size of the go-unirest patches and make rebasing them easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment