.merges

vtnerd: please also PR 7285 against release (if you want)

moneromooo: you could PR the p2p / rpc limit patch now

Looks like at least one of vtnerd's patches is on only one of master/release.

binary_buffer in one branch, byte_slice in the other.

afaik we did not merge this to branch because it was not a bug fix

ok

heya im just reading about multisig wallets and wow. Great work. it sounds awesome and super powerful. thank y'all!

vtnerd: please take a look at 7286 7287

How is waiting for an autistic person to get bored working out for you? While you settle in to your new way of life, think positively,you don't need to obsess over signs of FUK activity anymore.

jess: Get back to work immediately. This was supposed to be a challenge ^^

Still rollin' the RPC dice to get the tests green @ 7283 (test parallelism)

I having 12/12 bad peers,they all at 2263958 but seems auto ban doesn't work for those IPs

Unable to sync without the blocklist

Consensus kinda relies on having at least one honest peer. There's a system that will drop a random peer from time to time to try and avoid those 100% sybils cases, but if your known peer list is 100% sybils, you're out of luck.

aichi-japan: Which version are you running?

i am runing lastest master

Can you try using the release-v0.17 branch?

100% sybils not in the beginning, I synced for about 10+ minutes from 1-2 normal nodes

Does anyone have any details on the new OOM attack going around?

Send a packet dump if you have one, I can have a look.

It's hard to catch them since my node is always restarting after failiure, but I do have some friends having touble with setting it up that way. Is there going to be a fix anytime soon?

Typically a couple days after I get a new packet. Then it should switch to a different one after a release.

gives voice to agentpatience

about capturing the OOM attacks, is there a preferred was to capture via a IDS/IPS firewall system like Fortigate?

I have a patch to dump traffic. Let me find and paste it...

monero-project/monero #7287 needs a second review

selsta reviewed, found one typo (?)

thanks :)

FUK has been extemely hostile to Monero for over 4 years. Making miners for Monero, making a pool for Monero, making code that Monero copied, not exploiting bugs to steal millions from exchanges. Wow. Such huge hostility.

moneromooo: monero-project/monero #7286#discussion_r553482752

if I understand this correctly vtnerd meant to set the defaults to p2p defaults, not size_t max

Ah. No.

Though I guess if he does PR that, fair enough. But if we can supply defaults, it makes sense to have no limit by default I think.

ok

Unless he can find a call from P2P that's not setting the restricted defaults of course.

But then the fix is to set the defaults.

.merge+ 7286 7287

Added

anything else for this release that is super important?

the suggestion was "defensive" programming - make the defaults restricted in case its neglected in a new call

vtnerd: if you want to include 7285 in release please PR it now to release branch

<selsta> "anything else for this release that is super important?" -> there is a deadlock bug, am working on a fix atm

we did fix one regarding ban list but there might be more

hm, might be this one, i was running .8 release, not master

this is the one we fixed, but we had more deadlock reports

or "freeze" reports

"monero-project/monero #7237" -> huh, yep, i caught this one

If it's a strong preference I guess I can change it, my preference isn't too strong. It just feels off.

(about default limits)