<k​iersten5821:matrix.org> the binary monero-gen-trusted-multisig is not working. is this a known issue?

<k​iersten5821:matrix.org> ```

<k​iersten5821:matrix.org> ./monero-gen-trusted-multisig --scheme=5/6 --filename-base test

<k​iersten5821:matrix.org> This program generates a set of multisig wallets - use this simpler scheme only if all the participants trust each other

<k​iersten5821:matrix.org> Monero 'Fluorine Fermi' (v0.18.4.5-release)

<k​iersten5821:matrix.org> Logging to ./monero-gen-trusted-multisig.log

<k​iersten5821:matrix.org> Generating 6 5/6 multisig wallets

<k​iersten5821:matrix.org> Enter password for new multisig wallets:

<k​iersten5821:matrix.org> Confirm password:

<k​iersten5821:matrix.org> Error: Error creating multisig wallets: Messages don't have the expected kex round number.

<k​iersten5821:matrix.org> ```

<k​iersten5821:matrix.org> 5/6, 3/4, 2/3, all do not work

<k​iersten5821:matrix.org> not a big deal as i will make it manually but this is super annoying

<k​iersten5821:matrix.org> even 3/4 required like 4 rounds of copy pasting stuff

<o​frnxmr:xmr.mx> Yeah seems to be broken

<o​frnxmr:xmr.mx> According to log, it isnt even connecting to my daemon

<k​iersten5821:matrix.org> surprisingly it worked on a 2/2

<o​frnxmr:xmr.mx> Confirmed

<k​iersten5821:matrix.org> shoudl open an issue for this

<k​iersten5821:matrix.org> shoudl open an issue for this, i need to make a gh acc

<o​frnxmr:xmr.mx> Im checking some older versions to see when it last worked

<t​orir:matrix.org> Github can shadowban if you sign up with a VPN, so check while signed out to see if your issue is actually visible to others.

<o​frnxmr:xmr.mx> 17.3.2 fails with diff error "Error: Error creating multisig wallets: Kex message unexpectedly empty."

<o​frnxmr:xmr.mx> 18.0.0 : "Error: Error creating multisig wallets: Messages don't have the expected kex round number."

<o​frnxmr:xmr.mx> 17.0.0 works

<o​frnxmr:xmr.mx> I imagine this is culprit monero-project/monero #8190

<o​frnxmr:xmr.mx> Landed in 17.3.2

<o​frnxmr:xmr.mx> cc vtnerd @rbrunner7:monero.social monero-project/monero #7877

<r​brunner7:monero.social> Without checking anything, I don't think that something in the `wallet2` multisig code is the culprit. If there was something fundamentally wrong in there regarding creating multisig wallets in the latest code, I am pretty sure we would know already for a long time. What I suspect is that `monero-gen-trusted-multisig` doesn't use the updated / modified API correctly, or in other w<clipped message>

<r​brunner7:monero.social> ords, is waiting for a modification that became necessary because of that. I am not sure, but I think the MMS isn't able to create wallets anymore either, for maybe a very similar reason.

<o​frnxmr:monero.social> It worked up til 17.3.2

<o​frnxmr:monero.social> And post 17.3.2, it only works for 3/3 4/4 etc wallets. Not threshhold like 2/3 or 3/4

<o​frnxmr:monero.social> The only related change i see, is the linked pr that modified kex

<o​frnxmr:monero.social> But yeah. I dont think its multisig code, just bug or incompatability introduced from that pr. Generating musig wallets manually works ofc

<p​lowsof:matrix.org> kiersten: you asked if an outside observer can tell exactly who signed the multisig transaction - this would remove an attractive amount of plausible deniability for those in a 2 of N wallet

<k​iersten5821:matrix.org> what about an inside observer? that is helpful still

<a​namoly424:matrix.org> Hello,

<a​namoly424:matrix.org> I have a bug for monero-oxide ( github.com/monero-oxide/monero-oxide ) that comes under :

<a​namoly424:matrix.org> "High

<a​namoly424:matrix.org> Incompatibilities with the targeted Monero consensus protocol which would require reimplementing notable sections of monero-oxide"

<a​namoly424:matrix.org> on immunefi, but, I CANNOT use immunefi because it needs an ID/KYC for new accounts to submit bugs. How can I contact monero-oxide other than immunefi, submit the bug with POC and proof and get the bounty ?

<a​namoly424:matrix.org> Also, the reason I am asking it here is the : page states that

<a​namoly424:matrix.org> "Bugs which cause panics, or a similar denial-of-service, are to be reported to the administrators (via Matrix) and the affected downstream projects (again via their stated disclosure methods).

<a​namoly424:matrix.org> A public disclosure will only occur once monero-oxide releases a fix."

<a​namoly424:matrix.org> and

<a​namoly424:matrix.org> "All affected projects should be privately disclosed to via their stated disclosure method (or any private means of communication upon lack of stated disclosure method)."

<a​namoly424:matrix.org> Also as I said before it comes under scope listed in immunefi and for very obvious reasons immunefi has made it as hard as possible for people to report bugs so i cannot do it via that either

<k​ayabanerve:matrix.org> Anamoly: Please open a GH security advisory or less preferable, message a maintainer of monero-oxide, such as myself, on Matrix.

<a​namoly424:matrix.org> There aren’t any published security advisories, I am messaging you right now though

<k​ayabanerve:matrix.org> You're able to submit security issues via GitHub for repositories which have enabled it. We have for monero-oxide Anamoly:

<k​ayabanerve:matrix.org> github.com/monero-oxide/monero-oxide/security

<k​ayabanerve:matrix.org> "Report a vulnerability" is a button to do exactly that

<a​namoly424:matrix.org> matrix.monero.social/_matrix/media/…matrix.org/sOuDMFBOCRhjvoDVDClLzfeC

<a​namoly424:matrix.org> its not letting me submit it..

<a​namoly424:matrix.org> the button it just shows a cross on my mouse and isnt enabled when i try

<k​ayabanerve:matrix.org> Fascinating. I have no idea then. Messaging me is justified, feel free to do so.

<a​namoly424:matrix.org> Yes, I have sent you a message

<k​ayabanerve:matrix.org> (I'd prefer GH as then it'd auto-sub boog900 but we'll manage)

<a​ck-j:matrix.org> The button works on my account FWIW