Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cached touch policy #30

Closed
deadc0de6 opened this issue Nov 11, 2017 · 6 comments
Closed

cached touch policy #30

deadc0de6 opened this issue Nov 11, 2017 · 6 comments

Comments

@deadc0de6
Copy link

Is there a way to set the touch policy to cached when using a yubikey for pgp and ssh ?

Found a way to do it for PIV (https://developers.yubico.com/PIV/Introduction/Yubico_extensions.html) but ykman doesn't seem to provide that option.

@emlun
Copy link
Member

emlun commented Nov 14, 2017

Sorry, no, there isn't. The hardware supports this for PIV only. We might add this feature (still for PIV only) to ykman sometime, but nothing is decided about it at this point.

@emlun emlun closed this as completed Nov 14, 2017
@emlun
Copy link
Member

emlun commented Nov 14, 2017

Wait, sorry, actually it's already implemented in ykman. Still only for PIV, though.

@deadc0de6
Copy link
Author

ok thanks

@tyhicks
Copy link

tyhicks commented Aug 26, 2019

@emlun can you point me in the right direction for requesting hardware support of cached touch policy for OpenPGP? It makes sense that this ykman issue was closed out since the hardware support isn't there so I think the next step is to request hardware support.

@dagheyman
Copy link
Contributor

@tyhicks Happy to inform you that any device with firmware version 5.2.3 or higher supports cached touch policy for OpenPGP. You'll need ykman 3.1.0 to set it.

@tyhicks
Copy link

tyhicks commented Aug 27, 2019

@dagheyman That's great to hear! I'll have to upgrade to a 5 series device sometime soon and give it a shot. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants