monzero-core.git/src/crypto/crypto.cpp, branch v0.11.0.1 Monzero core node, command-line wallet, consensus code, and release tooling. https://code.monzero.org/monzero-core.git/atom?h=v0.11.0.1 2017-08-23T12:38:03Z crypto: use malloc instead of alloca 2017-08-23T12:38:03Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2017-08-20T20:19:29Z urn:sha1:b5345ef4f08eee2b7e36853ca3efede44ab4a091 crypto: moved boost::lock_guard into a smaller scope 2017-06-22T09:11:15Z stoffu stoffu@protonmail.ch 2017-06-19T23:27:31Z urn:sha1:8da82256d475656a8a4932b9e2d623f80c7e62e6 Signature proving payment to destination by only revealing key derivation, not the actual tx secret key 2017-06-22T09:11:13Z stoffu stoffu@protonmail.ch 2017-03-29T23:22:16Z urn:sha1:c9e0e944e900012b5789fd54bd8e455e399f94a0 update copyright year, fix occasional lack of newline at line end 2017-02-21T17:38:18Z Riccardo Spagni ric@spagni.net 2017-02-21T17:38:18Z urn:sha1:c3599fa7b94764d8f1cf7828a3f3a46067efe359 Preliminary support for DragonFly BSD 2016-12-15T10:27:53Z Antonio Huete Jimenez tuxillo@quantumachine.net 2016-12-15T10:27:53Z urn:sha1:b00da61eab03df2268a2c9946e03385a7d38a5fb - It builds but no further testing has been done. rct amount key modified as per luigi1111's recommendations 2016-08-28T20:30:19Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-08-10T11:48:20Z urn:sha1:d4b62a1e295a7fb19de6081733b1d8e0610cbf08 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 moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-08-28T20:24:19Z urn:sha1:e70e8a69f4611914a97aa2c856cbbb262945a186 crypto: fix compile error: use named type in sizeof 2016-05-18T05:01:58Z redfish redfish@galactica.pw 2016-05-18T04:52:01Z urn:sha1:6462a3a6db8452523b8c07d8394fbc5dc86f7295 Btw, the warning 4200 remains disabled, but it did not get triggered (GCC 6.1.1, ARM). But, perhaps a better way than disabling the warning would be to do what is suggested here: http://stackoverflow.com/questions/3350852/how-to-correctly-fix-zero-sized-array-in-struct-union-warning-c4200-without%3E crypto: make clear generate_random_bytes is not thread safe 2016-05-14T23:05:59Z moneromooo-monero moneromooo-monero@users.noreply.github.com 2016-05-14T21:08:10Z urn:sha1:d539be33590f7dfb0013187502744286f2959ee3 And add a thread safe version to encourage proper use Use boost::thread instead of std::thread 2016-03-11T15:09:50Z Howard Chu hyc@symas.com 2016-03-11T12:25:28Z urn:sha1:b937a2c915861900d047d4d4a24af31c454e3540 and all other associated IPC