• 0 Posts
  • 10 Comments
Joined 2 months ago
cake
Cake day: April 26th, 2025

help-circle
  • Yeah, why not? I’ll go ahead and make that suggestion.

    What? Do you understand what I’m asking? Do you understand what you’re suggesting?

    I mean, the terminal allows them to ctrl-c, ctrl-v a simple solution developed by someone else, even if that someone else didn’t bother to build out a GUI for applying their changes.

    So googling how to do someone, copy/pasting command is better than finding it in GUI? How high are you?

    The convoluted steps they would have to take to achieve the same effect with a GUI would seriously hinder the GUI-only user.

    Again a solved problem, just make a decent GUI for your application.





  • It is. It’s just… how do you know you’re actually talking to the fingerprint sensor and not a fake one that’s been plugged in?

    Think of it like a locked mailbox: the fingerprint sensor might securely match the fingerprint and only unlock if it’s correct—but if anyone can swap out the mailbox with their own lookalike, and the OS just blindly accepts the “unlocked” signal, the whole security model breaks. Without an attestation mechanism (like SDCP on Windows or secure enclave-backed verification), the OS can’t prove it’s getting input from trusted hardware. Match-on-chip helps, but it’s not enough unless the result is cryptographically signed by the sensor and validated by the OS through a trusted, authenticated channel.

    That’s the gap in Linux: there’s no widely adopted standard for verifying that trust path end-to-end.