Linker error about tiny-aes-c HOT 5 CLOSED

No this is entirely intended and not at all incorrect :)

#include-ing a C source file is not a recommended practice in C-programming.
I think it takes place more often in C++ code bases, but it is not a recommended practice with C modules.

You need to add aes.c to the list of C-files being compiled, otherwise you will get a linker error.
And yes that error can be solved in some instances by including the C-file.

I will not explain further why this is not a recommended practice.
See these posts from StackOverflow (first hits on google) for more information on why this is not a good practice.

https://stackoverflow.com/questions/232693/including-one-c-source-file-in-another
https://stackoverflow.com/questions/11334371/cant-we-include-c-file
https://stackoverflow.com/questions/11849868/is-it-ok-to-include-a-c-file-in-another-c-file

from tiny-aes-c.

Yeah ok, thanks. Again, really nice fucking library. One question though, have you ever thought about implementing XTS?

from tiny-aes-c.

I did not know that particular mode of operation before googling it. It seems like a twist on CTR mode from glancing quickly through a description.

I have not implemented CTR nor XTS myself, but am pretty sure some of the forks of this project has done CTR mode. Not sure about XTS though. Would need to look through the forks or spend some time googling - I'm online through my phone now, so basically AFK ;)

It's typically not horribly difficult to implement a new mode of operation, so maybe you got the chops for it yourself? :) I' gladly help you.

ECB is sort of the basic primitive that other modes build upon. CBC is a good example to learn from :)

from tiny-aes-c.

Oh and by the way @fullnitrous , forgot to thank you for the kind words :)

from tiny-aes-c.

Yeah no problem, i'll close this for now. Though i might implement those other modes of operation if i ever get the time to :)

from tiny-aes-c.