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
In addition to that, it could be interesting to allow for signing WACZ files using self-signed "single-use" certificates that would be generated on the fly by js-wacz directly, like archiveweb.page does for example.
js-wacz currently supports the "Domain-Name Identity + Timestamp Signing" portion of the WACZ Signing spec via the
--signing-url
and--signing-token
options.In addition to that, it could be interesting to allow for signing WACZ files using self-signed "single-use" certificates that would be generated on the fly by js-wacz directly, like archiveweb.page does for example.
This use case would fit under the "Anonymous Signing" portion of the WACZ Signing spec.
This feature would greatly benefit from the addition of a trusted timestamp, which the spec doesn't currently support: webrecorder/specs#142
The text was updated successfully, but these errors were encountered: