-
Notifications
You must be signed in to change notification settings - Fork 182
Comparing changes
Open a pull request
base repository: intel/tinycrypt
base: v0.2.8
head repository: intel/tinycrypt
compare: master
- 14 commits
- 12 files changed
- 9 contributors
Commits on Aug 31, 2017
-
When decrypting with CBC mode, the in and out buffers should be the same size. Even though the IV and ciphertext are contiguous, the in buffer points to the first byte of the ciphertext. The sanity check has been updated accordingly. Because of this error, the CBC mode tests are reporting the wrong size for the decrypted buffer (80 - 16 - 16 == 48 != 64). This has been corrected. Also, since the loop in the decryption is writing to the out buffer, the loop conditional has been changed to `n < outlen`. This should avoid any future errors if `inlen` changes so that it’s no longer equal to `outlen`.
Configuration menu - View commit details
-
Copy full SHA for da923ca - Browse repository at this point
Copy the full SHA da923caView commit details
Commits on Sep 2, 2017
-
Merge pull request #26 from rob-brown/master
Fix incorrect buffer size
hackermnementh authoredSep 2, 2017 Configuration menu - View commit details
-
Copy full SHA for 8a35f17 - Browse repository at this point
Copy the full SHA 8a35f17View commit details
Commits on Dec 15, 2017
-
Configuration menu - View commit details
-
Copy full SHA for 6a22712 - Browse repository at this point
Copy the full SHA 6a22712View commit details
Commits on Nov 20, 2018
-
Fix innocuous memset size bug in ECC test method
In one of the ECC auxiliary test methods, a buffer 'd' was being erased with memset using a wrong buffer size (NUM_ECC_WORDS instead of 4*NUM_ECC_WORDS). This bug was not affecting the correctness of ECC nor any other crypto primtive. In fact, it was not affecting even the ECC test itself since the content of such buffer was being overwritten rigth after the erasure procedure. This fix removes a warning triggered when compiling the code.
Configuration menu - View commit details
-
Copy full SHA for 323cd15 - Browse repository at this point
Copy the full SHA 323cd15View commit details -
Remove the name of Constanza Heath from AUTHORS as she is not maintaining the project anymore.
Configuration menu - View commit details
-
Copy full SHA for 8a3b3f7 - Browse repository at this point
Copy the full SHA 8a3b3f7View commit details
Commits on Nov 21, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 7c4ab60 - Browse repository at this point
Copy the full SHA 7c4ab60View commit details -
Merge pull request #35 from mped-oticon/issue30_vla
portabillity: Make unnecessary VLA into statically sized array
Configuration menu - View commit details
-
Copy full SHA for b7e3195 - Browse repository at this point
Copy the full SHA b7e3195View commit details
Commits on Feb 20, 2019
-
Use tests based on NIST SP 800-90A HMAC_DRBG testvectors. Signed-off-by: Thomas Ebert Hansen <[email protected]> Signed-off-by: Rafael Misoczki <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6e0eb53 - Browse repository at this point
Copy the full SHA 6e0eb53View commit details
Commits on Aug 8, 2019
-
Abstraction for architecture dependent secure memset.
In ecc_dh.c it is widely used to zero out the memory used for holding sensitive information, such as private keys. This memory is cleared by a memset, but as this is done right at function return, this memset will most likely be optimized out by the compiler, as the memory will no longer be used, hence no need to set it. To prevent the memset from being optimized out, it is necessary to place a memory barrier at the memset, but such a barrier is compiler depended. To solve the above, a _set_secure function has been introduced. This defaults to an inlined function calling memset and, in cases where the compiler defines __GNUC__, adds a memory barrier which ensures that the memset is not optimized out. For compilers, not defining the __GNUC__, it may be necessary to define TINYCRYPT_ARCH_HAS_SET_SECURE which then declares the _set_secure function extern, thus meaning that it will require target implementation, which in turn allows for architecture/compiler dependent implementation. This also fixes the memset's in uECC_make_key and uECC_make_key_with_d which actually was missing the memory barrier. Fixes #32 Signed-off-by: Danny Oerndrup <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 28b33ec - Browse repository at this point
Copy the full SHA 28b33ecView commit details
Commits on Sep 4, 2019
-
Merge pull request #38 from daor-oti/master-set_secure
Abstraction for architecture dependent secure memset.
Configuration menu - View commit details
-
Copy full SHA for 484f51f - Browse repository at this point
Copy the full SHA 484f51fView commit details
Commits on Sep 6, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 87d74dd - Browse repository at this point
Copy the full SHA 87d74ddView commit details
Commits on Sep 10, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 3db4aa9 - Browse repository at this point
Copy the full SHA 3db4aa9View commit details
Commits on Sep 17, 2019
-
Merge pull request #40 from winnietwo/side_channel_patch
Patch for #39 Sidechannel resistence of uECC_sign disabled
Configuration menu - View commit details
-
Copy full SHA for 5969b0e - Browse repository at this point
Copy the full SHA 5969b0eView commit details
Commits on Mar 5, 2024
-
Configuration menu - View commit details
-
Copy full SHA for cf24c90 - Browse repository at this point
Copy the full SHA cf24c90View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.2.8...master