sure

done, I think

triggered a build to make sure it works

<fluffypony "triggered a build to make sure i"> Yep, looks great. Thanks!

Hi guys, how to re-login multisig wallet?

This post just has brand new creation, not how to login a existing multisig wallet

Guest_48: I don't understand what you mean with "re-login a multisig wallet". Can you please elaborate the situation you are in?

moneromooo: You still looking for testers for the Monero Update thing? If so, which OS is most needed?

(testing wise)

Always :) Windows was a massive pita, iDunk spent hours on it. If you do try windows, it'll crash till a new version of gpgme.

Otherwise, less common ones that still support Qt I guess.

OK, will make a thread on Reddit then later

ty

Which jason parser would you recommend to connect to monero-wallet-rpc via C libcurl? Minimalistic perfered.

json-c

Assuming plain C, that is

Looks promising.

What is your opinion about this library? zserge.com/jsmn It has a very small footprint. But I'm not sure that's sufficient.

Never worked with it

fair enough. You wouldn't happen to have a very simple example of json-c in use!? e.G. get_version or get_balance from monero-wallet-rpc or so.

is there any reason Monero doesn't use include guards?

nonie_: Sorry, it's been years since I've worked with it. Nowadays I only use C++, so had no use for json-c

FWIW primo uses cJSON to talk to monerod.

peach34: Maybe because "#pragma once" is better and simpler?

cJSON (Ultralightweight JSON parser) nice, nice.

rbrunner I don't see that much where I'm looking either

But yeah I agree

xiphon: stoffu: I added remember-where-a-tx-came-from-to-drop-if-invalid to 5968 and you had reviewed that PR before, you might want to check the addition.

moneromooo: kk

xiphon: also can you check whether you're ok with my last comment in 6103 ?

peach34: Maybe I was lucky! I just randomly grabbed this and found it there: github.com/monero-project/monero/blob/master/src/daemon/daemon.h

moneromooo: acked it

ty

sure, np

Anyone with established history wants to add their (long term) signing pubkey to the gitian checker ? You would not have to post sigs every release without fail.

i don't think i've ever posted my sig elsewhere so i dunno if its useful.. .? i made a key once upon a time

does it work with gpg curve25519 keys or does it need to be rsa?

If you want to try to build gitian on releases and PR to gitian.sigs, it'd be useful.

It will work with whatever GPG likes.

i think the version in debian stable supports it

is there anything that could prevent a coredump being written?

monero-wallet-gui segfaulted on me and I didn't get a coredump, I'm currently trying to reproduce it with gdb attached

ulimit, /proc/sys/kernel/core_pattern, read only filesystem, ENOSPC, possibly some capability.

moneromooo: i've just noticed that with v0.15 there is still a burst of about 4MB of data when the wallet initially connects to the server, i seem to recall from a few months ago that it was possible to instruct the server to compress the data stream (via curl back then) and it turned into something like 600KB. do you know what it is about?

Is it a trusted daemon ?

yes

4 MB seems like a lot. I don't recall seeing that.

I'll add to the list to look at. Low priority though.

it's especially noticeable over tor as you might imagine

simple tcpdump should provide enough evidence, i recall back then that the options to compress were already available server-side, but not client-side, and I thought the client woudl eventually land support for compressing and never thought about it again

but i'm back to using onion services now and ran into the same thing, so just fyi

Was your wallet synced btw ?

If not, it syncs.

Just making sure :P

yeah about 1000 blocks behind

and it does sync

just takes a very long time (minutes) to kickstart the process over onion

while the background data transfer is happening, the wallet just says "Starting refresh ..." and is unresponsive

Were those 1000 blocks about 4 MB ? :)

or "Refreshing" ..

I thought about that, but it was also 4MB months ago. too much of a coincidence I think, but I can also check with a synced wallet if you wish

oh

client<->server rpc is encrypted now?

that's new

so much for the manual curl :p

but good development!

i'll look at this with more time tomorrow. should still be possible, but tcpdump is useless in this case. take care!

you can turn off SSL still

curl does ssl auth just fine.

yeah but you have to bend over backwards to tcpdump it

in OpenLDAP we use layered protocol modules and we can stick a "debug" module anywhere into the stack. so we can do plain protocol -> network socket, or plain -> debug -> socket (and when debugging is on, gives hex/alpha dump of in and out traffic)

and plain -> debug -> ssl -> debug -> socket

Sure. I'm not claiming anything about tcpdump.

although usually the debug output below the SSL layer isn't much interesting

I did have a patch to dump traffic if that helps. It's in a closed patch, should be findable with "dump".

but this way we can always see our traffic, even if SSL or GSSAPI or IPsec security layers are in use

I'm not sure whether it dumps SSL or before though...

What do people think of mms rpc ? It's meant to make multisig easier to use, so it doesn't really make sense for rpc I think.

It's not invasive though I guess.

(I've not read the patch yet)