promag: right, but we shouldn't introduce a user exposed crasher over a spurrious test failure...
in any case, I'm not married to the idea of reverting it, but that should be our _default_ response to serious bugs found in an RC esp when there isn't a really straight forward and clear fix.
dongcarl Looks like it's not permissions, but related to the fact that inside depends/x86_64-pc-linux-gnu/lib, libexpat.so & libfreetype.so are symlinks
libexpat.so: symbolic link to libexpat.so.1.6.8
libexpat.so.1.6.8: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, not stripped
fanquake: Okay thanks, I’ll take a look on when back behind keyboard. Your setup is documented in the link you sent?
peers of this type pretend to be running various versions of Bitcoin software, but are not. they respond with compact blocks handshakes, pings and pongs, but never respond to headers, get blocks, or inventory messages. the addr messages they push are stuffed with like-peers, and in general seem to be over represented in outgoing connections of normal nodes.
the current discovered peers are all on VPS hosts, carefully chosen to evade the logic which prevents connecting to multiple peers in the same /24. there's a sample of them here, representing GCE, AWS, DigitalOcean, and Hetzner. https://pastebin.com/raw/Q5wzqvg2