Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Commented Apr 14 at 15:45
  • 3
    Let's first quell the misgiving. YubiKey and most other security keys do not require or use any sort of online connectivity as that would be antithetical to their purpose. Commented Apr 14 at 16:22
  • There 3 ways I know you can do this without "Linux programing" which I have no experience with also. 1 go the route of making your own device, you'll want something to act as a "rubber ducky" weather it's a pico, arduino, or other microcontroller and have it enter your password. 2. Use a YubiKey and set your password to either the touch actions (this is what I do for low security applications) 3. Use a YubiKey and set up the login system to allow login via the fido passkeys, this is the proper secure way of doing things and I believe YubiKey has instructions for this Commented Apr 14 at 16:29
  • Not an answer because I may have misunderstood the question. There are many posts that show how to detect a button press, a simple one is raspberrypihq.com/use-a-push-button-with-raspberry-pi-gpio . If you then want the Pi to inform ANOTHER Linux box of the event, you will need to study inter-machine communications, but that is too advanced for a single question. Commented Apr 14 at 19:19
  • @DanHolli: To be fair. The original Yubico OTP feature – which was the sole feature of the Yubikey once upon a time, before "most other security keys" – did generally require access to the Yubico API in order to validate the OTPs out-of-the-box, unless you reprogram it with a custom key first (which then makes it not work with websites that validate OTPs against the main API, so it was not done often by individuals). And since it was advertised as a method of secure logon to websites, it certainly was not "antithetical to their purpose". Commented Apr 15 at 19:02