-
Notifications
You must be signed in to change notification settings - Fork 23
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
Certificate pinning issue after bunq certificate renewal #123
Comments
Any details about the fix of this issue? |
Is the problem just the pinned key?
|
yes, this should be new key: |
Sweet. Should we do a PR? Or is this already planned for a release?
…On Thu, 26 Mar 2020 at 19:10 masoudparvari ***@***.***> wrote:
Is the problem just the pinned key?
SANDBOX(
"public-api.sandbox.bunq.com",
"v1",
"sha256/9Y+oZve6H+r17Kdn+lN5sT0ijgxLyDGIuQtUwLupawA="
);
yes, this should be new ky:
sha256/SEJfjAW74vHQmGe/lb9NwBjzAw5y7rpJH3UWpGE5q8A=
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#123 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE33FBX6UWULSXQR4UOTWDRJOK7LANCNFSM4LR5SOXQ>
.
|
I have a patch for ourselves. But I can't push a branch and do a pull request. |
Hi guys! Thanks for bringing this up :) To enable you to keep using our SDKs, a PR has been submitted just now that will update the certificate hash. I'll close this issue when the PR is merged so you know when you can continue building great applications with our amazing API! |
Steps to reproduce:
What should happen:
What happens:
SDK version and environment
Extra info:
Apparently your old certificate has expired in Wednesday, 21 April 2021 at 14:00:00. And that's hard coded in code.
The text was updated successfully, but these errors were encountered: