Posts by JustinDerrick@mstdn.ca
 (DIR) Post #B5c2hUFK0hBxZwweFE by JustinDerrick@mstdn.ca
       1 likes, 0 repeats
       
       @enigmatico @nicole4fox Depends on how technical you want to get - but essentially, you have asymmetric keys - a private portion and a public portion.  If you generate a strong hash (SHA-256) of a document, then encrypt that hash with your private key, and send that signature along with the file, the recipient can generate their own SHA-256 hash of the document, then decrypt the signature using the private key. If the decrypted hash matches the generated hash, you know the document hasn’t been altered in transit, and that the only person who could have generated that signature is the person who holds the private key. The pubic key would be published somewhere (a directory, or the person’s website) so you could verify its authenticity. More complex systems are built on this, but at their core it’s a system built on private & public keys.
       
 (DIR) Post #BALTMULxvH73fy8ZWK by JustinDerrick@mstdn.ca
       0 likes, 0 repeats
       
       @nuintari @mxshift I didn’t realize they were that slow by modern standards…. But I’m guessing that even small-ish RSA keys (can modern tools even create RSA keys smaller than 2048-bit?)  would overwhelm an old 32-bit CPU.