Add simple description of usage about aes HOT 4 CLOSED

Dear Joachim Strömbergson Why does not support AES-192? Can you improve the project and add AES-192 feature Thank you ! Best Regards Mickey From: Joachim Strömbergson Sent: Friday, February 22, 2019 2:14 AM To: secworks/aes Cc: Subscribed Subject: [secworks/aes] Add simple description of usage (#4) 1. Load the key to be used by writing to the key register words. 2. Set the key length by writing to the config register. 3. Initialize key expansion by writing a one to the init bit in the control register. 4. Wait for the ready bit in the status register to be cleared and then to be set again. This means that the key expansion has been completed. 5. Write the cleartext block to the block registers. 6. Start block processing by writing a one to the next bit in the control register. 7. Wait for the ready bit in the status register to be cleared and then to be set again. This means that the data block has been processed. 8. Read out the ciphertext block from the result registers. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

Dear Joachim Strömbergson Thank you for your prompt reply. Best Regards Mickey From: Joachim Strömbergson Sent: Tuesday, March 12, 2019 5:01 PM To: secworks/aes Cc: mickey20111111 ; Comment Subject: Re: [secworks/aes] Add simple description of usage (#4) Hi! Thanks for the question. The reason for not supporting AES-192 is that in my experience, AES-192 is very rarely used in any applications ans use cases. Either AES-128 or AES-256 is being used. There difference in performance, key length etc is so small between AES-192 and AES-256 that if you need more than AES-128, AES-256 is what is used. Adding AES-192 would primarily complicate the key expansion. If someone would create a patch (with updates for test cases etc) for it, I would be happy to add support for AES-192. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.