gui.xmr.pm/files/block.txt has 2 new entries

Even with v0.17.1.5-release and the blocked nodes the attacker eventually gets my node

Kronovestan: run sync_info

I just closed and reopened my node...

do you use the latest version of the block list?

selsta, do I do that when it shows 2 blocks off?

selsta, well since last night

we are working on a new release, in the meantime we have to use the block list workaround

gotcha

i updated the block list today

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

so 1) update to the latest block list, if you still have this issue please post the output of "sync_info"

will do!

that file right

yes

I'll keep this open please update when you update the block list.

selsta: currently got the block height issue, here is my sync_info: paste.debian.net/1175252

not currently running the blocklist because I had never seen the issue on my own node until just now

Lyza: do you use CLI or GUI?

Lyza 66.70.255.248 is on the block list

anyway, apply the block list, it is the only solution for this at the moment until we have a new release out

if you use CLI you can ignore it completely, the CLI can transact fine even with +2 difference

yeah feather also is working :)

yea they patched it

Did already somebody tell luigi1111 that the cert for xmr.llcoins.net expired 3 days ago? Some Reddit user noticed this today.

I know about it just forgot to update

Alright :)

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 (monero-project/monero #7041). I'll try to seed passphrase and resync the wallet.

lh1008: can you post the daemon logs to the Github issue?

And wallet.

yes, selsta I will, will share it when done.

.merges

moneromooo: fails to compile for me and also CI paste.debian.net/hidden/84b120b9

MDINFO ? MGINFO or MINFO ?

Ah, I removed the G on the dev VM, mistakenly it seems.

"[51.83.81.237:12641 OUT] Claims 2243634, claimed 2243635 before"

for some reason this message has to be appear twice before a peer gets kicked

Is that too conservative ?

I thought from the commit title they would get kicked after doing it once. But the current behaviour is fine if it is intended.

It's gonna not do that anymore soon anyway.

yep, twice is fine, avoids getting kicked when doing pop_blocks

So is this an actual bad actor or just some random stupid code hanging around?

Bad actor.

Same one who was Sybil attacking the network previously, most likely.

glad they are providing their services for free for hardness testing

Absolutely 😀

It's not free for them :wink:

I wonder if he's funding all this from miner donations

this is still AHP's ? But changed modus operandi?

*aliens*

How much do 165 VMs at OVH cost anyway?

hmm, they're actually quite cheap

couple $$/month each