1
$\begingroup$

Is Tiny AES algorithm any different from the standard AES algorithm? I have come across mentions of Tiny AES at a lot of places but none which define it's architecture.

$\endgroup$
  • $\begingroup$ from the readme, "This is a small and portable implementation of the AES ECB, CTR and CBC encryption algorithms written in C." $\endgroup$ – Richie Frame Nov 22 '19 at 7:20
  • $\begingroup$ So, is it safe to assume that the algorithms are exactly the same? $\endgroup$ – Tarun Mittal Nov 22 '19 at 8:17
  • $\begingroup$ @TarunMittal yes. $\endgroup$ – Legorooj Nov 22 '19 at 8:34
  • $\begingroup$ Thank you for the help :) $\endgroup$ – Tarun Mittal Nov 22 '19 at 8:36
  • 1
    $\begingroup$ You'd probably hurt yourself not using a better wrapped authenticated encryption API. $\endgroup$ – DannyNiu Nov 22 '19 at 8:49
2
$\begingroup$

"Normal" AES implementations and tiny-AES perform the same task.

As stated in the README:

This is a small and portable implementation of the AES ECB, CTR and CBC encryption algorithms written in C.

It's simply an implementation with low memory usage. The reason for the existance of tiny-aes can be traced back to the initial search for a replacement for DES (which would then become AES). One of these requirements were that they should have low memory usage for implementations suitable for example in SmartCards.

As stated in their paper (Second AES candidate conference, section 5) they performed tests on the different submitted AES candidates, one of which was memory usage.

$\endgroup$
  • 2
    $\begingroup$ One may want to note that this implementation makes no claims about (cache) timing side-chanell resistance if that is something one is worried about. $\endgroup$ – SEJPM Nov 22 '19 at 10:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.