-
Notifications
You must be signed in to change notification settings - Fork 17
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
SSL Pinning support #129
SSL Pinning support #129
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a couple of questions that I think are not blocking.
Sure @rahimrahman I can explain at some point in the near future about all this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly done with the review. One comment for my understanding
Summary
As part of some of the requirements by XXXXX we needed to add support for SSL Pinning when building your own app.
The way is being built is a combination of the app and the network-client library, the app will hold the certificate assets while the network-library will use these certs to verify the server trust.
The cert files should have either a
.crt
or.cer
extension while the name of the file must be the domain name.The reason we support two files extensions per domain is to be able to build the app taking into account server cert rotation and minimizing the amount of app distribution through updates in order to validate the certs.
This SSL Pinning certificates should be included in the app at build time.
Ticket Link
https://mattermost.atlassian.net/browse/MM-59055