You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see, we are utilising the subresource integrity (SRI) attribute here to protect from untrusted code being loaded into our application.
While we are fine with occasionally having to manually upgrade the SDK version we include, we are absolutely not fine with the content of that version just silently changing from under us, which is what happened when you re-released v2.0.37 yesterday (changing the SHA-384 hash from x+DMONHL5BGxlpfSXJ+v8DUZMGk+303t2BJCpdl/PJnePCjL2eHB6y9bA5V4dTsb to 9EPbYTFD7Oxlnn4s2sg+mfMtqdTzc1mWRudXMR1EBd9dsUlyuDab2OvDWf0Jolsy).
So we kindly ask whether you could refrain from reusing version numbers in the future if at all possible?
Thanks,
Niels
The text was updated successfully, but these errors were encountered:
Dear Zendesk Team,
we have an integration into Zendesk that includes a specific version of ZAF in the following way:
As you can see, we are utilising the subresource integrity (SRI) attribute here to protect from untrusted code being loaded into our application.
While we are fine with occasionally having to manually upgrade the SDK version we include, we are absolutely not fine with the content of that version just silently changing from under us, which is what happened when you re-released v2.0.37 yesterday (changing the SHA-384 hash from
x+DMONHL5BGxlpfSXJ+v8DUZMGk+303t2BJCpdl/PJnePCjL2eHB6y9bA5V4dTsb
to9EPbYTFD7Oxlnn4s2sg+mfMtqdTzc1mWRudXMR1EBd9dsUlyuDab2OvDWf0Jolsy
).So we kindly ask whether you could refrain from reusing version numbers in the future if at all possible?
Thanks,
Niels
The text was updated successfully, but these errors were encountered: