01:43:32 .merge+ 6965 6964 6963 01:43:32 Added 01:52:52 .merges 01:52:53 -xmr-pr- 6886 6963 6964 6965 01:52:58 .merge+ 6927 01:52:58 Added 02:46:08 -xmr-pr- moneromooo-monero opened pull request #6969: block_queue: sanity check on string length 02:46:08 -xmr-pr- > https://github.com/monero-project/monero/pull/6969 02:46:09 -xmr-pr- moneromooo-monero opened pull request #6968: block_queue: sanity check on string length 02:46:09 -xmr-pr- > https://github.com/monero-project/monero/pull/6968 03:01:08 -xmr-pr- ZRFLDF opened issue #6970: sync_info and height exception 03:01:08 -xmr-pr- > https://github.com/monero-project/monero/issues/6970 12:21:54 https://old.reddit.com/r/Monero/comments/jn687x/monerogui_prune_mode_always_2_blocks_behind/ 12:21:56 Will this particular issue also be fixed in the new release? 12:21:58 I remember another user reporting similar behavior a while ago, hence 13:16:09 -xmr-pr- moneromooo-monero opened pull request #6972: protocol: reject empty incoming block messages 13:16:09 -xmr-pr- > https://github.com/monero-project/monero/pull/6972 13:16:09 -xmr-pr- moneromooo-monero opened pull request #6971: protocol: reject empty incoming block messages 13:16:09 -xmr-pr- > https://github.com/monero-project/monero/pull/6971 14:14:37 luigi1111: you available today for merges / tagging? 15:25:49 Good News Everyone! my patch to add dependency lists to static libraries has been accepted in Gnu binutils https://sourceware.org/pipermail/binutils/2020-November/113989.html 15:26:13 this is only half of the functionality tho, I need to write the linker support still 15:26:39 but this feature can make some of the pain of e.g. linking libzmq go away. 16:11:54 Nice. Thanks. 16:34:20 nice one hyc 16:43:20 yes 17:18:12 .merges 17:18:12 -xmr-pr- 6886 6927 6963 6964 6965 17:21:36 yea still stuff missing in the merge list 17:21:55 but you can merge it for now 17:23:28 was afraid of that 17:24:09 moneromooo: block queue sanity check? are you going to close that? 17:25:29 Yes, the other one addresses the root cause. 17:26:02 Though I suppose it's double safer. 17:27:00 Closed. 17:30:53 6866, do we want that in ? Technically it protects against transient errors. 17:31:20 Whether there *are* errors that might be transient rather than permanent there is another debate... 17:32:10 .merge+ 6972 6966 6967 17:32:10 Added 17:33:18 moneromooo: maybe better for next release? 17:33:50 Oh yes, I meant in general, not for this one. 17:34:03 I was pondering closing it. 17:34:09 could you rebase 6962? 17:34:21 and then also PR the boost 1.66 change 17:37:31 6962 done 17:37:46 The other one I'll do once 6962 is merged since it'll also conflict. 17:39:51 ok also https://github.com/monero-project/monero/pull/6961 needs a branch approval 17:40:52 done 17:41:58 vtnerd: have you found anything else about dandelion you'd want in a release soon ? 17:42:47 .merge+ 6962 6961 17:42:48 Added 17:42:54 .merges 17:42:54 -xmr-pr- 6961 6962 6966 6967 6972 17:43:12 oki luigi1111w would be ready again for merges 18:38:24 yes, I have a patch that switches to fluff mode if no outbound connections are available 18:54:46 vtnerd: if you PR it now / next hours we can include it if it is easy to review 19:07:58 its a couple of lines of production code with a chunk of tests. just PR'ed 19:10:03 ty 19:14:49 .merge+ 6974 19:14:49 Added 19:14:51 .merges 19:14:51 -xmr-pr- 6961 6962 6966 6967 6972 6974 19:15:44 sorry i haven't been following AHP mitigation - are the detection / banning tools getting merged into a release? Or do node ops still need to manually detect and ban? 19:15:58 no 19:16:08 manually specify a block list 19:16:08 -xmr-pr- vtnerd opened pull request #6974: Switch to Dandelion++ fluff mode if no out connections for stem mode [... 19:16:08 -xmr-pr- > https://github.com/monero-project/monero/pull/6974 19:16:09 -xmr-pr- vtnerd opened pull request #6973: Switch to Dandelion++ fluff mode if no out connections for stem mode 19:16:09 -xmr-pr- > https://github.com/monero-project/monero/pull/6973 19:16:12 but some mitigations are included 19:25:02 ok. is at least your --ban-list PR in? or still gotta loop through a list 19:25:31 yes --ban-list is in 19:27:31 gingeropolous: btw they stopped mirroring block heights 19:27:41 they started doing other things now 19:28:26 selsta: would extremely long-lived connections that are in state "synchronizing" but actually never seem to be transmitting any data be one of them? 19:28:41 yes 19:29:10 and other things, see #6971 19:29:25 oh wow 19:29:46 i got a few of those connected right now 19:29:58 adding to blacklist :p 19:32:01 do we have an updated blacklist file, btw ? 19:32:31 https://gui.xmr.pm/files/block.txt 19:32:47 this one is complete, unless they added new IPs in the past days 19:35:03 thx 19:40:18 offtopic - i have had no luck finding an answer to this - does anyone know if a linux xen dom0 is capable of hibernating, and if yes, is there some way to have the memory dump be encrypted, perhaps by having to type a password at the serial console after resuming? 20:16:08 -xmr-pr- mj-xmr opened pull request #6975: Run Valgrind checks for any binary in a list mj-xmr 20:16:08 -xmr-pr- > https://github.com/monero-project/monero/pull/6975 22:24:47 kayront, the Qubes crowd might be able to help you with that.