04:01:07 the binary monero-gen-trusted-multisig is not working. is this a known issue? 04:01:08 ``` 04:01:10 ./monero-gen-trusted-multisig --scheme=5/6 --filename-base test 04:01:12 This program generates a set of multisig wallets - use this simpler scheme only if all the participants trust each other 04:01:14 Monero 'Fluorine Fermi' (v0.18.4.5-release) 04:01:16 Logging to ./monero-gen-trusted-multisig.log 04:01:18 Generating 6 5/6 multisig wallets 04:01:20 Enter password for new multisig wallets: 04:01:22 Confirm password: 04:01:24 Error: Error creating multisig wallets: Messages don't have the expected kex round number. 04:01:26 ``` 04:02:49 5/6, 3/4, 2/3, all do not work 04:05:26 not a big deal as i will make it manually but this is super annoying 04:05:36 even 3/4 required like 4 rounds of copy pasting stuff 04:23:23 Yeah seems to be broken 04:23:40 According to log, it isnt even connecting to my daemon 04:36:44 surprisingly it worked on a 2/2 04:41:14 Confirmed 04:43:35 shoudl open an issue for this 04:43:56 shoudl open an issue for this, i need to make a gh acc 04:45:40 Im checking some older versions to see when it last worked 04:45:59 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. 04:58:52 17.3.2 fails with diff error "Error: Error creating multisig wallets: Kex message unexpectedly empty." 04:59:23 18.0.0 : "Error: Error creating multisig wallets: Messages don't have the expected kex round number." 05:03:24 17.0.0 works 05:08:07 I imagine this is culprit https://github.com/monero-project/monero/pull/8190 05:10:58 Landed in 17.3.2 05:16:05 cc vtnerd @rbrunner7:monero.social https://github.com/monero-project/monero/pull/7877 06:11:22 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 06:11:22 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. 06:12:20 It worked up til 17.3.2 06:12:57 And post 17.3.2, it only works for 3/3 4/4 etc wallets. Not threshhold like 2/3 or 3/4 06:13:28 The only related change i see, is the linked pr that modified kex 06:15:46 But yeah. I dont think its multisig code, just bug or incompatability introduced from that pr. Generating musig wallets manually works ofc 11:51:50 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 14:44:15 what about an inside observer? that is helpful still 21:51:32 Hello, 21:51:32 I have a bug for monero-oxide ( https://github.com/monero-oxide/monero-oxide ) that comes under : 21:51:34 "High 21:51:36 Incompatibilities with the targeted Monero consensus protocol which would require reimplementing notable sections of monero-oxide" 21:51:38 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 ? 22:01:04 Also, the reason I am asking it here is the : page states that 22:01:04 "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). 22:01:06 A public disclosure will only occur once monero-oxide releases a fix." 22:01:08 and 22:01:10 "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)." 22:01:12 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 22:04:49 Anamoly: Please open a GH security advisory or less preferable, message a maintainer of monero-oxide, such as myself, on Matrix. 22:05:40 There aren’t any published security advisories, I am messaging you right now though 22:09:24 You're able to submit security issues via GitHub for repositories which have enabled it. We have for monero-oxide Anamoly: 22:09:45 https://github.com/monero-oxide/monero-oxide/security 22:09:59 "Report a vulnerability" is a button to do exactly that 22:10:30 https://matrix.monero.social/_matrix/media/v1/download/matrix.org/sOuDMFBOCRhjvoDVDClLzfeC 22:10:57 its not letting me submit it.. 22:11:47 the button it just shows a cross on my mouse and isnt enabled when i try 22:12:45 Fascinating. I have no idea then. Messaging me is justified, feel free to do so. 22:13:05 Yes, I have sent you a message 22:13:06 (I'd prefer GH as then it'd auto-sub boog900 but we'll manage) 22:13:15

The button works on my account FWIW