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
We built a Chrome extension that automatically reads and validates C2PA manifests.
It leverages c2pa-js in the background, which uses your library.
We noticed that some COSE signatures were not validated in the extension while it was when using the same library (c2pa) with the exact same manifest in a web app.
We created an issue in c2pa-js a few months ago.
We recently identified that the problem might come from c2pa-rs and not directly c2pa-js.
All the problematic signatures seem to use es256.
I provided a few examples and more context in the other issue.
Regards,
Clement from Digimarc
The text was updated successfully, but these errors were encountered:
Hi,
We built a Chrome extension that automatically reads and validates C2PA manifests.
It leverages c2pa-js in the background, which uses your library.
We noticed that some COSE signatures were not validated in the extension while it was when using the same library (c2pa) with the exact same manifest in a web app.
We created an issue in c2pa-js a few months ago.
We recently identified that the problem might come from
c2pa-rs
and not directlyc2pa-js
.All the problematic signatures seem to use
es256
.I provided a few examples and more context in the other issue.
Regards,
Clement from Digimarc
The text was updated successfully, but these errors were encountered: