The company behind the Saflok-brand door locks is offering a fix, but it may take months or years to reach some hotels.
  • sylver_dragon@lemmy.worldEnglish
    17·
    6 months ago

    From the unsaflok.com site:

    Dormakaba uses a Key Derivation Function (KDF) to derive the keys for some of the Saflok MIFARE Classic sectors. This proprietary KDF only uses the card’s Unique IDentifier (UID) as an input.
    Knowledge of the KDF allows an attacker to easily read and clone a Saflok MIFARE Classic card. However, the KDF by itself is not sufficient for an attacker to create arbitrary Saflok keycards.

    Security is hard. Cryptography is even harder. Don’t roll your own algorithms, it’s just asking for a problem. And given that “oversight”, I’d bet that the rest of the kill chain involves equally bad encryption or hashing being used on the cards.

    • ramble81@lemm.ee
      1·
      6 months ago

      I’m curious, for a non-network connected lock, how could you ensure that it’s secured with time bound parameters like they list?

      Now that I’m thinking about it I guess each lock would have a private key and a CMOS of sorts to keep time. The writer could then write have the public key of each room and that could have a timestamp as part of the encrypted payload. I guess to take it further you could reverse it too with that payload having a private key of the writer and the locks could verify the private key against a public key of the writer. At that point each writer would have to have the public key of all locks, and each lock would have the public key of each writer.

      At that point your payload to encode would be a timestamp of expiration and any sort of “checksum” or PSK to verify it was made by a valid writer?

  • Zeusbottom@sh.itjust.worksEnglish
    11·
    6 months ago

    In 2011 I was aghast when I learned a popular keycard / biometric system used FTP to pull down its cleartext list of acceptable keys from the server.

    The username was something like ADMIN and the password was PASS.

    And no, that wasn’t the FTP command; that was the password.

    So I’m not surprised that there are still problems with these devices.

    edit: more complete thought

    • NOPper@lemmy.world
      5·
      6 months ago

      To be fair to manufacturers for once here, this kind of this is usually due to users not properly securing these systems. The industry is still way behind on proper infosec but they’ve come a long way the last 10 years or so.

  • don@lemm.ee
    8·
    6 months ago

    Corporate shareholders: is it cheap? Yes? Do I ever stay there? No? tfw I don’t give a fuck lol