-
Notifications
You must be signed in to change notification settings - Fork 824
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
Use ai.moda's RFC3161 load balancer. #2523
Conversation
@Manouchehri: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. I understand the commands that are listed here |
Hello @Manouchehri, Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here. Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project. Please help complete the Mattermost contribution license agreement? This is a standard procedure for many open source projects. Please let us know if you have any questions. We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team. |
/check-cla |
Release Note
|
@Manouchehri Thank you for your contribution. |
Erm, what security reasons...? |
Ah, if your security team doesn't understand how TSAs and/or CAs work in general, then I can why they would mistakenly think either of those things matter. You're currently accessing your TSA over HTTP... so if your security team believes they need to personally "trust" the TSA endpoint (instead of trusting the certificates it signs with), they've already screwed up. |
Resolves #1229.
Disclosure: I made this load balancer. I'm a fan of timestamping.
Release Note