Closed JeyJeyGao closed 3 weeks ago
@JeyJeyGao Could you move this issue to notation-go
? As it's more a library issue than an external user facing one.
LGTM; Additionally, it would be good if we could implement a caching system that allows users to bring their own cache implementation. This would enable users to leverage in-memory caching (for libraries), disk-based caching (for binaries), or any other remote storage option for the cache. Providing this flexibility would give users more control over how the caching is handled in the system and at the same time reducing complexity from our code.
Cache is important and @JeyJeyGao will share the detailed design later.
We will use #425 (for notation-go) and https://github.com/notaryproject/notation-core-go/issues/125 (for notation-core-go) to track the CRL support of notation v1.3.0. Other future work items will be tracked in #428
Closing as completed.
As suggested in https://github.com/notaryproject/notation-core-go/issues/125, CRL support is required.
Here is the plan to complete CRL support based on priority:
base CRL
downloading and validation, with a fallback rule to automatically choose OCSP and fallback to CRL.