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
I configured my bitbucket account to have the public key associated with the keys stored inside my yubikey
Whenever i try to run git commands that is associated with submodules (It's a repository with over 15 submodules), multiple yubikey touches are prompted even though I've set the touch policy to cached
Note that setting the touch policy to ON would make git prompt a touch on every submodule operation, while CACHED only prompts for 2-3 touches (the amount of touches seem to be random)
Would there be any solution to this problem? If not, why is git prompting multiple yubikey touches? I've read that Yubikey cached touch policy caches the credentials for 15s, so I don't get why this is happening
I know that this might not be an issue on yubikey-manager's part, but I thought that this might be a good place to ask anyway
Thanks!
The text was updated successfully, but these errors were encountered:
Hey, so i've tried setting the touch policy of my Yubikey to
CACHED
I configured my bitbucket account to have the public key associated with the keys stored inside my yubikey
Whenever i try to run git commands that is associated with submodules (It's a repository with over 15 submodules), multiple yubikey touches are prompted even though I've set the touch policy to cached
Note that setting the touch policy to
ON
would make git prompt a touch on every submodule operation, whileCACHED
only prompts for 2-3 touches (the amount of touches seem to be random)Would there be any solution to this problem? If not, why is git prompting multiple yubikey touches? I've read that Yubikey cached touch policy caches the credentials for 15s, so I don't get why this is happening
I know that this might not be an issue on
yubikey-manager
's part, but I thought that this might be a good place to ask anywayThanks!
The text was updated successfully, but these errors were encountered: