View previous topic :: View next topic |
Author |
Message |
PIC24H
Joined: 02 Mar 2015 Posts: 19
|
Open SSL and AES En-/Decryption with ccs compiler |
Posted: Thu Apr 09, 2015 5:42 am |
|
|
Hello, has anyone had experience with openssl (aes) and the ccs compiler?
Or how to include the files into the project (c code)?
I have e-mailed ccs customer support and asked them if they got a crypto library, but unfortunately they dont.
My plan is to decrypt an hex file in the bootloader (ex_pcd_bootloader.c).
But I'm figuring out how to include the openssl stuff into that project.
Any helpful advice? |
|
![](templates/subSilver/images/spacer.gif) |
Ttelmah
Joined: 11 Mar 2010 Posts: 19383
|
|
Posted: Thu Apr 09, 2015 8:09 am |
|
|
Seriously, unless you have a very large PIC, forget it. I wrote a SSL library for a job, on a DsPIC and ended up using over 130K of code space for the security code.... |
|
![](templates/subSilver/images/spacer.gif) |
PIC24H
Joined: 02 Mar 2015 Posts: 19
|
|
Posted: Thu Apr 09, 2015 3:44 pm |
|
|
Ttelmah wrote: | Seriously, unless you have a very large PIC, forget it. I wrote a SSL library for a job, on a DsPIC and ended up using over 130K of code space for the security code.... |
So in your opinion that doesnt make sense? Should I use the xtea encryption instead? I'm using a pic24hj256 |
|
![](templates/subSilver/images/spacer.gif) |
RF_Developer
Joined: 07 Feb 2011 Posts: 839
|
|
Posted: Fri Apr 10, 2015 1:55 am |
|
|
PIC24H wrote: |
So in your opinion that doesnt make sense? |
The point is that the resources required to implement such encryption schemes are greater than those PICs generally provide. Another question that has to be asked is what is the problem to which using such an encryption scheme is the solution? Does it, in fact, provide any real extra security, and at what price in terms of development time and system resources? |
|
![](templates/subSilver/images/spacer.gif) |
Ttelmah
Joined: 11 Mar 2010 Posts: 19383
|
|
Posted: Fri Apr 10, 2015 6:31 am |
|
|
and particularly if he is talking about doing it in a bootloader.....
Tea, is a very good idea. The key here was that it is designed to be small. Xtea, was designed to be more secure, but came at the cost of being a little larger. However still much more 'PIC sized'.
For a bootloder in particular, if it needs great security, I have to say something is probably wrong with how it is being implemented. |
|
![](templates/subSilver/images/spacer.gif) |
|