Physical Buttons, trusted shell indication light and display

How many of you are annoyed by administrator password prompts?

I sure could use a non-spoofable* authorization button and console.

*(will need engineering and kernel integration, root cold spoof it anyway)


Here are the basic parts,
an lcd terminal, distinct from the rest of the system, OR, a physical light that indicates that information on my screen is not just some elaborate userspace spoof of an authorization window.

This is not just a light that comes on when a sudo program is activated, it is a light that indicates that the video display is verified to be giving out authenticated information.

This information would include, the filename, and what access the program requests.

A hardware button could authorize things like software updates or installs (from authenticated repositories only)  with just a press.

A(the) hardware button could be used to confirm execution (or opening) of a newly downloaded file.

A(the) hardware button could be used to  authorize system settings changes..

For additional security, the system could be set to not prompt you for your passwords until you press the(another) button

Codes or patterns could be used for some authentication (morse code or a timer, or presses in response to a song or tones)

If there was a small(or any dedicated) display (a text display, ) this information could be presented on that display instead of the general purpose display.


I believe I heard of trusted computer initiatives before, but it sounds like it may be an alliance to own your computer, and not trust the user...  Perhaps some of the hardware could be repurposed for hardware authentication interrupts.



This feature is similar to the reset buttons on our consumer routers, but this one would not reset data, and it could be manifested by a switch with a safety lock, or flip cover.

I imagine this button would not be on the keyboard, or if it is it would be one of those special keys like on one of the late 90's keyboards with buttons for everything.


I would like to make this project work with a Logitech G15 keyboard.
It has a little display, and it has tons of extra buttons...  but ultimately I would like the button to have it's own device, and only let the authentication program  read from it.

(It would otherwise be possible to have a web page spoof your password prompt, we are being conditioned to enter our passwords multiple times on every login and configuration change...  This would be a great way to authenticate routine maintenance, and enforce a more deliberate and communicative authorization process)