View Single Post
Old 08-29-2010, 11:30 PM   #9
joblack
Wizard
joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.joblack ought to be getting tired of karma fortunes by now.
 
Posts: 1,216
Karma: 1410408
Join Date: Jul 2006
Location: Somewhere on earth
Device: Kindle Paperwhite, Kindle DX, JBC, Onyx M92
Quote:
Originally Posted by pholy View Post
Ahh-ha! That makes sense - if the whole book was encrypted with the customer's key, each download would have to wait on encrypting a big file. As Charleski describes it, only the relatively short (1024 bits? whatever...) payload-key needs to be encrypted for each customer.

I think.... something like that...
Asymmetric encryption algorithms (like RSA) are a huge amount slower than the symmetric one.

Almost all public key encryption schemes (OpenSSH, ...) work the steps: decrypt symmetric key with asymmetric ones and then use the faster symmetric decryption (like RC4 or AES).

The pdf won't be changed later on. As far as I can see only the device key is adjusted. That's the reason why you can reauthorize a newer hardware with an Adobe ID.

The symmetric and asymmetric key remain the same only your decryption information for the asymmetric key has to be adjusted (because of the changed hardware information)
joblack is offline   Reply With Quote