aba46a7c5f
Merge pull request #221 from wowario/upstream
...
Upstream and other stuff
2019-06-26 06:57:43 -07:00
514328a65f
update checkpoints.dat
2019-06-26 14:06:45 +03:00
172966a0c3
simplewallet: tone down not mining warning
2019-06-26 14:06:44 +03:00
815d93ba24
faster sync from 0
2019-06-26 14:06:44 +03:00
94abe2280e
update Dockerfile
2019-06-23 20:28:16 +03:00
556ec3c144
simplewallet: don't ask about mining when running a command line
...
This is likely to be done via a script
2019-06-23 12:01:44 +03:00
ec42fd80a1
update PKGBUILD
2019-06-23 12:01:44 +03:00
805781957a
silent no incoming connections warning
2019-06-23 12:01:44 +03:00
03e49575a4
bump version to 0.6.1.2
2019-06-23 09:12:11 +03:00
4f262b2de9
set background mining to No
2019-06-23 09:09:39 +03:00
5563c65f64
rename to wownero
2019-06-23 09:05:11 +03:00
adbb7229af
blockchain_export: allow exporting blocks.dat format from pruned
...
We don't need any of the pruned data for this
2019-06-23 08:14:37 +03:00
e49f7450d2
daemon: display peer address type in print_cn
2019-06-23 08:13:01 +03:00
10593e20a5
tx_sanity_check: don't print an error when not enough outs to check
2019-06-23 08:11:47 +03:00
517d5e6915
rpc: work around a GCC 7.4.0 (at least) bug
...
In static member function ‘static boost::optional<cryptonote::rpc::output_distribution_data> cryptonote::rpc::RpcHandler::get_output_distribution(const std::function<bool(long unsigned int, long unsigned int, long unsigned int, long unsigned int&, std::vector<long unsigned int>&, long unsigned int&)>&, uint64_t, uint64_t, uint64_t, const std::function<crypto::hash(long unsigned int)>&, bool, uint64_t)’:
cc1plus: warning: ‘void* __builtin_memset(void*, int, long unsigned int)’: specified size 18446744073709551536 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
2019-06-23 08:11:13 +03:00
24bbd442a3
core: do not complain about low block rate if disconnected
...
In that case, we'll still keep the "Monero is now disconnected
from the network" near the end of the log
2019-06-23 08:10:25 +03:00
f15de92f90
blockchain: silence an error getting blocks for pruned nodes
...
This happens often when a pre-pruning node asks a pruned node
for data it does not have
2019-06-23 08:08:55 +03:00
2e9b9d92fc
db_lmdb: commit pruning txn at checkpoints
...
to avoid errors when the txn is too large
2019-06-23 08:06:28 +03:00
eb189153ca
p2p: don't forget pruning seed or public RPC port when updating peers
...
Older nodes don't pass that information around
2019-06-23 08:06:00 +03:00
6755e0d7f3
p2p: propagate out peers limit to payload handler
2019-06-23 08:04:26 +03:00
d46fb70930
p2p: close the right number of connections on setting max in/out peers
2019-06-23 08:04:17 +03:00
39e9fa05b8
core: fix --prune-blockchain not pruning if no blockchain exists
2019-06-23 08:00:10 +03:00
9afbcfb777
Merge pull request #217 from wowario/wow
...
update RandomWOW submodule
2019-06-17 07:16:57 -07:00
e6c875a954
rpc: restrict the recent cutoff size in restricted RPC mode
2019-06-17 12:35:03 +03:00
12085c4c74
ensure no NULL is passed to memcpy
...
NULL is valid when size is 0, but memcpy uses nonnull attributes,
so let's not poke the bear
2019-06-17 12:34:54 +03:00
2a5f743d0a
abstract_tcp_server2: improve DoS resistance
2019-06-17 12:34:44 +03:00
2fb6c1f80d
serialization: check stream good flag at the end
...
just in case
2019-06-17 12:34:11 +03:00
8ad9d0f618
tree-hash: allocate variable memory on heap, not stack
...
Large amounts might run out of stack
Reported by guidov
2019-06-17 12:30:40 +03:00
ddafd99cac
cryptonote: throw on tx hash calculation error
2019-06-17 12:30:31 +03:00
26276d5df7
serialization: fail on read_varint error
2019-06-17 12:30:23 +03:00
de536f49cb
cryptonote_protocol: fix another potential P2P DoS
...
When asking for txes in a fluffy transaction, one might ask
for the same (large) tx many times
2019-06-17 12:30:16 +03:00
3fdf63bc90
cryptonote_protocol: expand basic DoS protection
...
Count transactions as well
2019-06-17 12:30:07 +03:00
2f402f9a45
cryptonote_protocol_handler: prevent potential DoS
...
Essentially, one can send such a large amount of IDs that core exhausts
all free memory. This issue can theoretically be exploited using very
large CN blockchains, such as Monero.
This is a partial fix. Thanks and credit given to CryptoNote author
'cryptozoidberg' for collaboration and the fix. Also thanks to
'moneromooo'. Referencing HackerOne report #506595 .
2019-06-17 12:29:59 +03:00
307bd8f5ae
epee: basic sanity check on allocation size from untrusted source
...
Reported by guidov
2019-06-17 12:29:47 +03:00
bc3aa2ea12
update RandomWOW submodule
2019-06-17 10:48:13 +03:00
94390f8364
Merge pull request #216 from wowario/upstream
...
Upstream
2019-06-14 05:46:17 -07:00
5249d14063
Merge pull request #215 from wowario/masterb
...
bump version to 0.6.1.1 and update checkpoints.dat
2019-06-14 05:46:05 -07:00
9713b3f058
Merge pull request #214 from wowario/master
...
Fix Windows detection
2019-06-14 05:45:54 -07:00
6f2d52de9e
Merge pull request #213 from fuwa0529/fix-no-ring
...
[need testing] hotfix "no ring" error in wallet
2019-06-14 05:45:40 -07:00
949158eb00
Merge pull request #212 from Aluisyo/patch-4
...
added super fast public node (wow.aluisyo.network)
2019-06-14 05:45:25 -07:00
c749be7f9d
Use 9 digit build IDs
2019-06-14 13:49:20 +03:00
036cdfadad
Delete redundant cppzmq dependency
2019-06-14 13:48:57 +03:00
8670b67c9c
Allow parallel make
2019-06-14 13:48:40 +03:00
98f2524ecc
Don't use -march=native
2019-06-14 13:48:26 +03:00
a0b181f4cd
[depends] update openssl to 1.0.2r
...
- This addresses https://www.openssl.org/news/secadv/20190226.txt (CVE: 2019-1559) which impacted all versions of openssl-1.0.
Note that this does not address CVE-2019-1543 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1543 ), which impacts all versions of openssl 1.1 through 1.1.0j and 1.1.1b.
The above (1.1) is patched in openssl, where it was marked as low severity. Similar issues possibly present in monero, should be looked into w.r.t. CVE-2019-1543.
2019-06-14 13:48:07 +03:00
2ae11e8e4b
cmake: do not use -mmitigate-rop on GCC >= 9.1
...
It was removed, but it still accepted by the compiler, which warns
for every file
2019-06-14 13:47:44 +03:00
ae9de01824
Fix GCC 9.1 build warnings
...
GCC wants operator= aand copy ctor to be both defined, or neither
2019-06-14 13:47:11 +03:00
5227b3280c
p2p: fix GCC 9.1 crash
2019-06-14 13:46:56 +03:00
ed34ba0774
epee: fix SSL autodetect on reconnection
2019-06-14 13:46:38 +03:00
33634f6dfd
miner: fix double free of thread attributes
...
issue: #5568
2019-06-14 13:45:07 +03:00
jw