yubikey-touch-detector(1)

πŸ“¦
version 1.15.0 Β· 4 versions
, in arch rolling

✨ yubikey-touch-detector ✨

okay so bestie, welcome to yubikey-touch-detector(1) β€” the little General Commands Manual page that's about to become your whole personality πŸ’… this is the tool that tells you when your YubiKey is literally sitting there waiting for a touch, and honestly? iconic behaviour.


🌸 NAME 🌸

yubikey-touch-detector β€” detects when a YubiKey is waiting for a touch. that's it, that's the vibe 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

yubikey-touch-detector [options...]

yes queen, just run it with whatever options you want ✨


πŸŽ€ OPTIONS πŸŽ€

  • -notify β€” shows desktop notifications. like, on your actual screen. so you can't miss it πŸ’–
  • -notify-title title β€” sets the desktop notification title template. defaults to "YubiKey is waiting for a touch".
  • -notify-body body β€” sets the desktop notification body template. defaults to "Touch your YubiKey to continue ({{.Reasons}})."
⚠️ heads up bestie, both the notification title and body use Go template syntax. {{.Reasons}} expands into a sorted, comma-separated list of the active event types: gpg, hmac, and u2f. so cute, so organised 🧚
  • -no-socket β€” disables the unix socket notifier. no socket for you πŸ™ˆ
  • -stdout β€” prints notifications to stdout. for the terminal girlies πŸ’»
  • -dbus β€” supports notifications via dbus SessionBus.
  • -v β€” enables debug logging. messy but make it diagnostic πŸ”₯
  • -version β€” prints version information and exits. bye bestie, love you πŸ‘‘

πŸ’œ DESCRIPTION πŸ’œ

yubikey-touch-detector detects when a YubiKey is waiting for a touch configuration. it's designed to be integrated with other UI components so they can display a visible indicator. so basically it's the backstage main character that makes everyone else look good ✨


🌈 ENVIRONMENT 🌈

  • YUBIKEY_TOUCH_DETECTOR_VERBOSE β€” equivalent to specifying -v.
  • YUBIKEY_TOUCH_DETECTOR_NOTIFY β€” equivalent to specifying -notify.
  • YUBIKEY_TOUCH_DETECTOR_NOTIFY_TITLE β€” equivalent to specifying -notify-title.
  • YUBIKEY_TOUCH_DETECTOR_NOTIFY_BODY β€” equivalent to specifying -notify-body.
  • YUBIKEY_TOUCH_DETECTOR_STDOUT β€” equivalent to specifying -stdout.
  • YUBIKEY_TOUCH_DETECTOR_NOSOCKET β€” equivalent to specifying -no-socket.
  • YUBIKEY_TOUCH_DETECTOR_DBUS β€” equivalent to specifying -dbus.

like, every option gets a little environment-variable twin. siblings! 🫢


πŸ“ FILES πŸ“

  • $XDG_RUNTIME_DIR/yubikey-touch-detector.socket β€” the socket exposing events on Linux 🐧
  • $TMPDIR/yubikey-touch-detector.socket β€” the socket exposing events on macOS 🍎

different paths, same energy πŸ’…


⭐ EVENTS ⭐

these are the events emitted over the socket, no cap:

  • GPG_1 β€” when a GPG operation starts waiting for a touch.
  • GPG_0 β€” when a GPG operation stops waiting for a touch.
  • U2F_1 β€” when a U2F operation starts waiting for a touch.
  • U2F_0 β€” when a U2F operation stops waiting for a touch.
  • MAC_1 β€” when a HMAC operation starts waiting for a touch.
  • MAC_0 β€” when a HMAC operation stops waiting for a touch.

see the pattern? _1 means it started, _0 means it stopped. slay, consistent ✨


πŸ‘‘ SEE ALSO πŸ‘‘

ykman, pam_u2f(8) β€” go read those too, iykyk πŸ“š


πŸ’€ LICENCE πŸ’€

yubikey-touch-detector is distributed under the ISC licence. periodt.


okay that's the whole page, bestie πŸ’– this was yubikey-touch-detector(1) from the General Commands Manual, dated 2026-09-21 β€” go touch your YubiKey, it's literally waiting for you πŸŽ€πŸ¦‹βœ¨

πŸ“¦ where this page comes from