.merge+ 6965 6964 6963

Added

.merges

.merge+ 6927

Added

Will this particular issue also be fixed in the new release?

I remember another user reporting similar behavior a while ago, hence

luigi1111: you available today for merges / tagging?

Good News Everyone! my patch to add dependency lists to static libraries has been accepted in Gnu binutils sourceware.org/pipermail/binutils/2020-November/113989.html

this is only half of the functionality tho, I need to write the linker support still

but this feature can make some of the pain of e.g. linking libzmq go away.

Nice. Thanks.

nice one hyc

yes

.merges

yea still stuff missing in the merge list

but you can merge it for now

was afraid of that

moneromooo: block queue sanity check? are you going to close that?

Yes, the other one addresses the root cause.

Though I suppose it's double safer.

Closed.

6866, do we want that in ? Technically it protects against transient errors.

Whether there *are* errors that might be transient rather than permanent there is another debate...

.merge+ 6972 6966 6967

Added

moneromooo: maybe better for next release?

Oh yes, I meant in general, not for this one.

I was pondering closing it.

could you rebase 6962?

and then also PR the boost 1.66 change

6962 done

The other one I'll do once 6962 is merged since it'll also conflict.

ok also monero-project/monero #6961 needs a branch approval

done

vtnerd: have you found anything else about dandelion you'd want in a release soon ?

.merge+ 6962 6961

Added

.merges

oki luigi1111w would be ready again for merges

yes, I have a patch that switches to fluff mode if no outbound connections are available

vtnerd: if you PR it now / next hours we can include it if it is easy to review

its a couple of lines of production code with a chunk of tests. just PR'ed

ty

.merge+ 6974

Added

.merges

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?

no

manually specify a block list

but some mitigations are included

ok. is at least your --ban-list PR in? or still gotta loop through a list

yes --ban-list is in

gingeropolous: btw they stopped mirroring block heights

they started doing other things now

selsta: would extremely long-lived connections that are in state "synchronizing" but actually never seem to be transmitting any data be one of them?

yes

and other things, see #6971

oh wow

i got a few of those connected right now

adding to blacklist :p

do we have an updated blacklist file, btw ?

this one is complete, unless they added new IPs in the past days

thx

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?

kayront, the Qubes crowd might be able to help you with that.