monzero-core.git/src/crypto, branch v0.10.1

oaes_lib: fix a leak on OOM error path

2016-12-10T12:51:20Z

found by coverity

wallet: fix output collision detection for view wallets

2016-11-07T18:59:30Z

View wallets do not have the spend secret key, and are thus unable to derive key images for incoming outputs. Moreover, a previous patch set key images to zero as a means to mark an output as having an unknown key image, so they could be filled in when importing key images at a later time. That later patch caused spurious collisions. We now use public keys to detect duplicate outputs. Public keys obtained from the blockchain are checked to be identical to the ones derived locally, so can't be spoofed.

Changed to ..._HASHBITS everywhere for consistency

2016-10-29T13:59:06Z

Dropped "bit" from bitmonero.

2016-09-26T21:22:30Z

cmake: transitive deps and remove deprecated LINK_*

2016-09-18T06:56:26Z

Keep the immediate direct deps at the library that depends on them, declare deps as PUBLIC so that targets that link against that library get the library's deps as transitive deps. Break dep cycle between blockchain_db <-> crytonote_core. No code refactoring, just hide cycle from cmake so that it doesn't complain (cycles are allowed only between static libs, not shared libs). This is in preparation for supproting BUILD_SHARED_LIBS cmake built-in option for building internal libs as shared.

crypto: armv7: slow-hash: remove redundant source include

2016-09-18T06:56:26Z

aesb.c is already present in libcrypto as a standalone object. Tested: builds and runs fine on armv7, static and dynamic.

Add ARMv8-A AES support

2016-09-16T00:45:49Z

More than twice as fast as plain C code. Note that both ARMv7 and ARMv8 can be further improved with better use of NEON. Also tweak ARMv7 multiplier

crypto,cmake: enable ASM mul impl on ARM; add cmake opt

2016-09-04T06:46:35Z

This was disabled earlier as part of diagnosing failing tests on ARM, which turned out to be due to aliasing, fixed by adding -fno-strict-aliasing. So, re-enabling it back.

rct amount key modified as per luigi1111's recommendations

2016-08-28T20:30:19Z

This allows the key to be not the same for two outputs sent to the same address (eg, if you pay yourself, and also get change back). Also remove the key amounts lists and return parameters since we don't actually generate random ones, so we don't need to save them as we can recalculate them when needed if we have the correct keys.

crypto: error out where appropriate

2016-08-28T20:28:29Z