• UndercoverUlrikHD@programming.dev
    link
    fedilink
    English
    arrow-up
    4
    ·
    7 hours ago

    Wouldn’t biometric data be sensor/implementation specific. I doubt the fingerprint data stored on an iPhone is the same as the one stored on an Xperia.

    • unexposedhazard@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      7 hours ago

      Your fingerprint is your fingerprint. If its possible to extract the raw data, then that can be reconstructed into your fingerprint…

      • kn33@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        That’s the thing - it’s not possible. The fingerprint is only ever stored within the fingerprint module, with no method for retrieval. The only thing the phone sees is “did this person scan a matching fingerprint or not?”

      • thisbenzingring@lemmy.today
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 hours ago

        in the early 2000s when fingerprint readers started getting popular, my coworker and I decided to test them…

        super glue fumes, printer toner and scotch tape. that’s all that was ever needed to bypass the reader once you could isolate a good spot where someones finger left a good mark. like from drinking glass or a door knob

        I’m not sure if I’d ever trust a fingerprint to fully be a secure passkey

      • UndercoverUlrikHD@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 hours ago

        Yeah, but what would you do with it? Can you convert the bytes to work on any other sensor the victim may also use their fingerprint? Never looked into the real implementation details of the fingerprint hardware.

        • Natanael@slrpnk.net
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 hours ago

          Sometimes you can. Or just bruteforce a colliding pattern that matches to print that instead, because why not