Samir Kakkar

This is already supported, for the signature plugin and expected to work for verification plugin. Any bugs can be fixed separately.

@gokarnm thinks we can start directory spec implementation while working in parallel to close this. This is not a blocker to start.

As per @gokarnm , this is not a blocker to start implementation.

@dtzar - Could you elaborate if you are looking to do CRUD operation on keys stored locally or remotely? If remotely, are we just doing CRUD on the remote key...

This is already implemented for Plugins to specify the signing keys in signingkeys.json

Modified the issue description to just focus on Sign and Verify commands for RC-1. This limited scope was discussed and agreed in the NV2 meeting on 9/8/2022

There are two reasons to defer this after the first release 1. We have another way of filtering with certificate fingerprints. 2. The Gatekeeper timeout is no longer a restriction...

This capability is to allow signing with local keys and certificate (certificate chains).

@dtzar - I created a new issue related to helping users deal with CLI errors. Refer https://github.com/notaryproject/notation/issues/300

@priteshbandi - Could you confirm and close this issue is fixed as expected?