|
Message
From: Jonathan Valamehr<jkv@u...>
Date: Mon Oct 23 01:35:16 CEST 2006
Subject: [oc] AES128 Question
Yes I understand Hemanth but the inverse key is not an output of the AES core, I dont know where to access it. Everything you said makes perfect sense so if I could figure out how to access the inverse key I'll be fine. Thanks!
----- Original Message ----- From: Hemanth<hemanths@d...> To: Date: Wed Oct 18 13:37:36 CEST 2006 Subject: [oc] AES128 Question
> Hi Jonathan, > I am sorry for not being able to reply earlier, I have been > travelling a > lot and hardly have checked my mails in between. Hmm.. that was a > long > time back and dont remember exactly but if my memory is correct the > inverse key is the key that is output after an encryption is > completed. If > you observe, both data and key undergo a series of transformation > and at > the end there is both a garbled key and encrypted data coming out. > This > key is taken as the inverse key for decryption. Infact I have used > one set > of key pairs as default in my test bench. This information is also > explained in the FIPS document. > Hope this helps, > Hemanth > > While using the AES128 core (aes_crypto_core) I have come > across a > > problem; after encrypting data with a key and receiving an > output, how > > do I know what the inverse key is in order to decrypt the > output? I had > > an example from the fips document about AES so I was able to > test > > given their key and output key, and was successful in doing > so. > > However, making up a key wont work for me as I have no idea > what the > > inverse key is. Clearing this issue up would really help me > out. Thanks. > > _______________________________________________ > > http://www.opencores.org/mailman/listinfo/cores > > > ----------------------------------------- > Stay ahead of the information curve. > Receive EDA news and jobs on your desktop daily. > Subscribe today to the EDA CafeNews newsletter. > [ http://www10.edacafe.com/nl/newsletter_subscribe.php ] > It's informative and essential. > This message was sent to you from a machine at 128.88.255.123 > >
|
 |