• jet@hackertalks.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 months ago

    This seems interesting. But for something so complex I would really like them to have a white paper to see how they achieve this.

    https://eprint.iacr.org/2023/189 Other systems, for instance, use a third party network to broadcast the parts of the secret that are needed to decrypt over time. So you’re relying on a third-party service, and if that third party service disappears you can’t unencrypt

    • Markaos@lemmy.one
      link
      fedilink
      arrow-up
      5
      ·
      4 months ago

      It’s a very short Python script and I’m confident I get the general idea - there’s absolutely nothing related to current time in the decryption process. What they refer to as a “time lock” is just encrypting the key in a loop (so the encrypted key from one loop becomes the plain text for the next one) for the specified duration and then telling you how many iterations were done. That number then becomes a second part of the password - to decrypt, you simply provide the password and the number of iterations, nothing else matters.