This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AES Encryption for TIVA Devices

Other Parts Discussed in Thread: AES-128

Dear all,

I fond this library for AES encryption on the link 

http://www.ti.com/tool/AES-128

Also I found another set of sample code provided by Tivaware for different types of AES namely 

AES CBC

AES CCM

AES ECB

and AES GCM on the examples folder for the TIVA 129 device.

I am new to AES encryption and I want to know what is the difference between this pure C library provided by TI and the other examples provided for the 129 series.  I understand this question may have errors and also may  be not up to the standards. I hope you understand that I am new to this encryption world and provide me with some starting point. 

I have a set of TCP/IP packets I need to encrypt and send to a server over the internet using a GSM module connected to my TIVA device (I have both a 129 and a 123) via UART 115200 BAUD. I was thinking of going with AES GCM but them I found this pure C library which has no flavor of AES and i'm confused.

Whats the difference of these flavoured Tivaware APIs and the pure C library given by TI?

Please help, your responses would be highly appreciated. 

 

  • Hi Amalinda,

    Amalinda said:

    AES CBC

    AES CCM

    AES ECB

    and AES GCM on the examples folder for the TIVA 129 device.

        You will find more info about these by doing a search elsewhere in the internet. 

    - kel

  • please correct me if I am wrong, is the pure C AES Library provided by TI using the ECB mode? 

  • I'm actually in the process of learning. It seems a lot complex process with math and everything. So I just wanted to know if the pure C library was good enough.

    I found out the pure C is not best recommended. But is has a lot of advantages and is very clearly written. Therefore it is very attractive for a beginner to start with and pursue with testing. Basically that pure C library would encrypt a given char, say, "A" at anytime to give the same output.  Therefore even if Mr.cracker doesn't know what data being sent, he knows that "SAME" data is being Transmitted every time an identical packet it TXed.

    But for my application I don't mind the attacker knowing this. I just don't want him to decrypt it. 

    What are the other drawbacks of this method, ECB?  Anyone already know willing to shed some light? A personal experience not shared in application notes, slaa397a, slau458c, spma021b, spmu367,spra740.

    thanks.

  • Amalinda said:
    personal experience not shared in application notes, slaa397a, slau458c, spma021b, spmu367,spra740.

    My friend - do you realize that your potential helpers are, "none too gently" forced now to read those 5 App Notes - to insure they don't, "invite your wrath!" (via reporting things you (now) know!)   Is that good - is it fair/proper?  (Root canal seems about as "pleasant" - this reporter will pass...)