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
Hi together,
I am thinking about an in-memory-cache for entering the smartcard-pin when using smimesign. I saw this already in other programs like git with the credentials-helper, which supports an in-memory-cache. Wouldn't that be a great feature to add this as a commandline-flag? Used with git for signing commits would then not require entering the scmartcard-pin for every commt.
Glad to hear what you think.
The text was updated successfully, but these errors were encountered:
The PIV standard requires no cache for signing.
Some smartcards / yubikey can be configured for caching the authentication of a key.
But I guess the signing software will not be able to control this.
I also "need" this, my employeer started to use GitLab self-host, and we started to use x509 to sign the commits. But when I got a branch which I need do a rebase, it asked me 42x to inform the pin to unlock the smartcard to read the certificated...
Hi together,
I am thinking about an in-memory-cache for entering the smartcard-pin when using smimesign. I saw this already in other programs like git with the credentials-helper, which supports an in-memory-cache. Wouldn't that be a great feature to add this as a commandline-flag? Used with git for signing commits would then not require entering the scmartcard-pin for every commt.
Glad to hear what you think.
The text was updated successfully, but these errors were encountered: