Re: encryption question

FWIW, one big lesson I learned about public key encryption is that it is
very slow and basically unusable for large streams, where large is defined
in a few hundred bytes or more. The solution is to generate a random key,
then encrypt that using the private key, then encrypt the rest using
symmetric encryption which is sensibly fast. Reverse the process to
decrypt.

My first attempt at encrypting/decrypting using public/private took about
5 seconds to read 2k of data. I felt that was too long! Re-doing it
"properly" meant it became "instant", but just as secure.

/Matthew Jones/
.

Relevant Pages

  • Re: British ISPs Block Wikipedia
    ... Public key encryption does not depend on a one-way maths operation ... Public key encryption and decryption is extremely processor intensive, ... is encrypted with one of many possible encryption algorithms that use ...
    (uk.legal)
  • Re: British ISPs Block Wikipedia
    ... Public key encryption does not depend on a one-way maths operation ... Public key encryption and decryption is extremely processor intensive, ... is encrypted with one of many possible encryption algorithms that use ...
    (uk.legal)
  • Re: A New Twist On Copyright Infringement?
    ... That is essentially the way subscription satellite TV works. ... The only way public key encryption ... This is just one way Randy's "Fully Secure Encrypted Media Format" ...
    (rec.audio.pro)
  • Re: security system
    ... >the decryption key from M. ... Public key encryption is slower than non-public key encryption, ... If what you actually want is to build a secure peer-to-peer file transfer ...
    (sci.crypt)
  • Re: security system
    ... >>C1...CN are not trusted and therefore they cannot have the decryption ... If a file is encrypted you can't use a hash of the decrypted ... >>of hashes and encryption where the hash of the encrypted file is the ... > Public key encryption is slower than non-public key encryption, ...
    (sci.crypt)