Expected behavior
Verbose logs should print that it was searching in the windows cert store. Bonus points if that log also provides where exactly it searched and what it found "Issue To" or the SHA1 Hash or something would be helpful.
Actual behavior
A clear and concise description of what actually happened.
Describe the bug
When using the local (windows) certificate store to find a cert the
CertificateStoreService
prints that its searchin in Azure Key Vault, because the log message was likely copied from the azure key vault provider. See: https://github.com/dotnet/sign/blob/ac9e8b416cd6e8692f1eea1ac6678d7e5c464216/src/Sign.SignatureProviders.CertificateStore/CertificateStoreService.cs#L118Uses the same resource key as: https://github.com/dotnet/sign/blob/ac9e8b416cd6e8692f1eea1ac6678d7e5c464216/src/Sign.SignatureProviders.KeyVault/KeyVaultService.cs#L79
which is: https://github.com/dotnet/sign/blob/ac9e8b416cd6e8692f1eea1ac6678d7e5c464216/src/Sign.Core/Resources.resx#L190-L192
Not sure of the semantics of TrustedSigningService but that service is also reusing that resource key: https://github.com/dotnet/sign/blob/ac9e8b416cd6e8692f1eea1ac6678d7e5c464216/src/Sign.SignatureProviders.TrustedSigning/TrustedSigningService.cs#L70
Expected behavior Verbose logs should print that it was searching in the windows cert store. Bonus points if that log also provides where exactly it searched and what it found "Issue To" or the SHA1 Hash or something would be helpful.
Actual behavior A clear and concise description of what actually happened.
Additional context