aboutsummaryrefslogtreecommitdiff
path: root/src/ringct/rctOps.cpp (follow)
AgeCommit message (Collapse)AuthorFilesLines
2018-07-05crypto: remove slight bias in key generation due to modulomoneromooo-monero1-6/+4
2018-06-06ringct: remove an unnecessary scalarmultBase in zeroCommitmoneromooo-monero1-4/+1
2017-12-18check accessing an element past the end of a containermoneromooo-monero1-0/+3
2017-12-16move includes around to lessen overall loadmoneromooo-monero1-0/+1
2017-12-07add a version of ge_double_scalarmult_precomp_vartime with A precompmoneromooo-monero1-0/+9
2017-12-07ringct: add a version of addKeys which returns the resultmoneromooo-monero1-0/+5
2017-03-22ringct: move ge_frombytes_vartime failure error to warningmoneromooo-monero1-11/+13
Avoids scaring people when seeing some invalid txes
2017-01-16Change logging to easylogging++moneromooo-monero1-0/+3
This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels.
2016-12-04ringct: switch to Borromean signaturesShen Noether1-1/+14
2016-10-23ringct: some more small optimizationsmoneromooo-monero1-48/+11
2016-10-15ringct: avoid unnecessary memcpymoneromooo-monero1-16/+3
2016-10-15ringct: add a few consts where possiblemoneromooo-monero1-4/+4
2016-10-15ringct: pass vectors by const ref where possiblemoneromooo-monero1-2/+2
2016-08-28ringct: remove unused codemoneromooo-monero1-245/+0
2016-08-28ringct: use memcpy/memset instead of handwritten loop where appropriatemoneromooo-monero1-29/+11
2016-08-28ringct: remove spurious copiesmoneromooo-monero1-24/+4
2016-08-28rct amount key modified as per luigi1111's recommendationsmoneromooo-monero1-14/+4
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.
2016-08-28rct: make the amount key derivable by a third party with the tx keymoneromooo-monero1-7/+13
Scheme design from luigi1114.
2016-08-28rct: use the already defined H where possiblemoneromooo-monero1-2/+1
Found by luigi1111w
2016-08-28ringct: optimization/cleanup of hash functionsShen Noether1-0/+25
2016-08-28ringct: "simple" ringct variantShen Noether1-0/+6
Allows the fake outs to be in different positions for each ring. For rct inputs only.
2016-08-28ringct: fix size unit mismatch calling keccakmoneromooo-monero1-1/+1
2016-08-28ringct: catch errors from ge_frombytes_vartimemoneromooo-monero1-11/+12
2016-08-28ringct: add functions to commit to an amountmoneromooo-monero1-0/+17
One to commit to an amount with zero key (for use with fake commitments for pre-rct outputs), and one with an arbitrary key (for rct outputs).
2016-08-28ringct: simplify random key generationmoneromooo-monero1-7/+2
2016-08-28ringct: cosmetic fixesShen Noether1-29/+3
Ported from Shen's RingCT repo
2016-08-28ringct: changes to hashToPointSimple to calcualte H2 valuesShen Noether1-0/+5
Ported from Shen's RingCT repo
2016-08-28ringct: compare keys with bitwise equality, not crypto opsShen Noether1-7/+6
Ported from Shen's RingCT repo
2016-08-28ringct: fix size argument to cn_fast_hashShen Noether1-1/+1
Ported from Shen's RingCT repo
2016-08-28ringct: lock access to the PRNGmoneromooo-monero1-2/+2
2016-08-28ringct: import of Shen Noether's ring confidential transactionsmoneromooo-monero1-0/+741
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 14:30:56 +0000