09:02:25 https://gui.xmr.pm/files/block.txt has 2 new entries 13:53:15 Even with v0.17.1.5-release and the blocked nodes the attacker eventually gets my node 13:53:38 Kronovestan: run sync_info 13:53:56 I just closed and reopened my node... 13:54:10 do you use the latest version of the block list? 13:54:11 selsta, do I do that when it shows 2 blocks off? 13:54:21 selsta, well since last night 13:54:43 we are working on a new release, in the meantime we have to use the block list workaround 13:54:51 gotcha 13:55:03 i updated the block list today 13:55:22 interestingly if I run it on a VPN with NO incoming connections then it's fine. It's like the attacker knows my public node IP and keeps hitting it 13:55:56 so 1) update to the latest block list, if you still have this issue please post the output of "sync_info" 13:56:22 will do! 13:56:35 https://gui.xmr.pm/files/block.txt 13:56:37 that file right 13:56:42 yes 13:57:23 I'll keep this open please update when you update the block list. 14:23:11 selsta: currently got the block height issue, here is my sync_info: https://paste.debian.net/1175252/ 14:23:27 not currently running the blocklist because I had never seen the issue on my own node until just now 14:31:33 Lyza: do you use CLI or GUI? 14:31:41 Lyza 66.70.255.248 is on the block list 14:31:58 anyway, apply the block list, it is the only solution for this at the moment until we have a new release out 14:32:20 if you use CLI you can ignore it completely, the CLI can transact fine even with +2 difference 14:32:50 yeah feather also is working :) 14:33:07 yea they patched it 15:47:53 Did already somebody tell luigi1111 that the cert for https://xmr.llcoins.net expired 3 days ago? Some Reddit user noticed this today. 15:48:49 I know about it just forgot to update 15:51:01 Alright :) 16:55:13 Hello everyone, I updated to latest version Monero Oxygen Orion v0.17.1.5 and the rpc error message showed again and both the wallet and the daemon are running with command `--log-level 2`. I didn't close the issue I had opened, so here I share it again (https://github.com/monero-project/monero/issues/7041). I'll try to seed passphrase and resync the wallet. 17:08:14 lh1008: can you post the daemon logs to the Github issue? 17:08:52 And wallet. 17:42:39 yes, selsta I will, will share it when done. 17:55:30 .merges 17:55:31 -xmr-pr- 6984 21:00:39 moneromooo: fails to compile for me and also CI https://paste.debian.net/hidden/84b120b9/ 21:04:58 MDINFO ? MGINFO or MINFO ? 21:40:58 Ah, I removed the G on the dev VM, mistakenly it seems. 22:03:01 "[51.83.81.237:12641 OUT] Claims 2243634, claimed 2243635 before" 22:03:12 for some reason this message has to be appear twice before a peer gets kicked 22:05:43 Is that too conservative ? 22:06:30 I thought from the commit title they would get kicked after doing it once. But the current behaviour is fine if it is intended. 22:06:59 It's gonna not do that anymore soon anyway. 22:10:27 yep, twice is fine, avoids getting kicked when doing pop_blocks 22:21:11 So is this an actual bad actor or just some random stupid code hanging around? 22:24:41 Bad actor. 22:24:41 Same one who was Sybil attacking the network previously, most likely. 22:25:05 glad they are providing their services for free for hardness testing 22:26:45 Absolutely 😀 22:32:26 It's not free for them :wink: 22:35:49 I wonder if he's funding all this from miner donations 22:36:36 this is still AHP's ? But changed modus operandi? 22:36:45 *aliens* 22:40:27 How much do 165 VMs at OVH cost anyway? 22:41:36 hmm, they're actually quite cheap 22:41:47 couple $$/month each