02:57:09 <QQ> FYI, in bulletproofs.cc there is a line that ends in two semicolons. Seems weird and useless. Is there some reason for it?
02:57:10 <QQ>     sc_mul(multiexp_data[i*2].scalar.bytes, a[ao+i].bytes, INV_EIGHT.bytes);;
02:57:23 <QQ> https://github.com/monero-project/monero/blob/907292dfb415df2ecbf6016d86e48531a3f14525/src/ringct/bulletproofs.cc#L176
10:34:05 <moneromooo> No, it's just a do-nothing statement.
12:59:31 <cohcho> moneromooo: What vm will you as the most secure to test malware inside?
13:01:33 <cohcho> hypervisor*
13:20:24 <Inge-> qubes?
13:23:12 <asymptotically> any are good. just be careful with things like 3d acceleration. at least with virtualbox's implementation, the guest can view things in video memory that weren't cleaned up properly
13:24:10 <moneromooo> Creating a SSL key takes a second every startup. I'm thinking of adding a mode where it's created once and stored in the wallet cache to be reused later. It means the daemon knows which wallet connects again, but it's fine if it's your daemon.
13:24:35 <moneromooo> Any opinion on this ? I think a passive adversary can also see what key is being used, right ?
13:26:40 <omartijn> Wouldn't the node already know which wallet it is from the IP address? Or are you thinking of wallets connecting to the node over TOR?
13:30:51 <moneromooo> If you come from the same IP address, then the daemon can tell, sure (though not at the wallet level). With Tor, you would not need SSL.
14:52:03 <gingeropolous> is the key generation done in its own thread, or does it block progression? 1 second on an independent thread seems like not that big of a deal
15:42:30 <moneromooo> Startup, blocking.
15:43:10 <moneromooo> Maybe it's not that big a deal, true. It does add up, but I guess I load wallets much more often that the average.
15:45:02 <omartijn> But you can already re-use certificates by giving an option when starting the wallet, right?
15:45:27 <omartijn> You just want to make that the default, and generate/store a certificate if not given
15:46:03 <moneromooo> Yes.
15:48:17 <cohcho> I've had the same problem due to frequent restarts and generated manually ssl certificate to avoid this delay.
15:51:49 <omartijn> I don't really see the added value, if you frequently restart the wallet you can already use a persistent certificate
15:52:38 <omartijn> Perhaps we could add a convenience option that checks for the certificate in the same directory as the wallet file, creates it if missing and otherwise loads it upon start
15:52:45 <omartijn> Something like --rpc-ssl-persist
15:55:49 <moneromooo> That's mostly pointless. If you're going to add an argument, you can add the existing one.