04:18:49 <selsta> 17:01 <Lyza> selsta can we throw in #7260 <-- will include it in next release
07:43:27 <rbrunner> bevanoff: I saw you mentioning here yesterday that you might start an attempt to implement multisig in the GUI wallet. I was the one implementing the thing named "MMS" in the CLI wallet, so I know a thing or two about multisig :)
07:43:38 <rbrunner> If interested I am available for chat about your project.
12:16:07 <PotCoiner> Hello
12:16:32 <selsta> .merge+ 7260 7295
12:16:32 <xmr-pr> Added
12:17:34 <selsta> .merge+ 7245
12:17:34 <xmr-pr> ...
12:17:37 <PotCoiner> Hello
12:36:11 <krabik2014> FUK has bееn intеnsеly hostilе to Monеro for ovеr 4 yеars. Making minеrs for Monеro, making a pool for Monеro, making codе that Monеro copiеd, not using bugs to stеal millions from еxchangеs. Wow. Such grеat hostility.
12:57:03 <Lyza> selsta great tyvm
13:04:05 <selsta> anyone else having issues with Tor tx-proxy?
13:04:14 <selsta> lost all Tor peers on all nodes
13:09:49 <Lyza> not using tor but I have out peers over i2p. no in peers atm though, had 4 yesterday
13:10:31 <selsta> I2P looks normal here, only Tor seems to have issues
13:14:34 <selsta> ok, now I’m getting a couple Tor peers again
14:14:41 <rbrunner> CLI wallet command 'sweep_all' does not sweep the whole wallet? Only the current account? So there is no command that simply empties the wallet, period?
14:15:48 <selsta> you can’t make a transaction over accounts
14:42:13 <rbrunner> You mean that's a protocol / transaction structure limitation, not only a missing command that I could program?
14:42:46 <selsta> It is intentional.
14:43:51 <selsta> (as far as I know)
14:44:27 <rbrunner> Yes, I dimmly remember that, fear not I won't program something, but still the question whether the protocol would allow it or not is interesting ...
14:45:29 <rbrunner> Somehow it's hard for me to believe that couldn't just grab everything and pack it in a single transaction.
14:47:32 <selsta> https://github.com/monero-project/monero/pull/2056 is usually good to read up on subaddresses
14:47:44 <selsta> and https://github.com/monero-project/research-lab/issues/7
14:47:51 <selsta> as far as I can see, you could program that
14:49:51 <selsta> but I don’t understand the math enough to 100% answer that :D
14:51:22 <rbrunner> Interesting, thanks :)
14:52:22 <moneromooo> It would allow it, it can't tell whether inputs are from the same account or not (thankfully).
14:55:27 <rbrunner> "thankfully" meaning you would run into all kind of problems if it did?
14:58:49 <moneromooo> Yes, like your privacy being invaded.
15:00:25 <rbrunner> Ah, ok. I was expecting something on a technical level.
15:01:50 <Lyza> feather should be able to do it if you import a wallet to it
15:01:59 <Lyza> since it doesn't have accounts
15:04:24 <rbrunner> Really? "No accounts" as in "no accounts yet", I guess? (It does take a mountain of work to implement that stuff, a whole hierarchy level.)
15:05:48 <Lyza> they have coin control for individual outputs, and no plans to ever implement accounts afaik
15:06:13 <Lyza> accounts are implemented inasmuch as the outputs will be recognized when importing a wallet, though
15:06:38 <rbrunner> Interesting.
15:07:42 <Lyza> can also label outputs, is pretty nice
15:10:35 <binaryFate> <selsta> anyone else having issues with Tor tx-proxy? <-- https://twitter.com/MinscTheRashemi/status/1348277018853519362?s=20
15:12:46 <hyc> I still have a number of in and out tor connections
16:32:05 <selsta> binaryFate: ok that makes sense, thanks
16:32:27 <selsta> hyc: I regained them on some nodes, but not on all
17:11:53 <i2per> use only i2p, lost all INC  previously had many
17:21:00 <sech1> selsta I have 141 peers connected now, none of them are from tor (no blocklist)
19:32:16 <agentpatience>  Hi Guys, Since I have been operating full node I m seeing a lot of bad behaviouron the network, i'm getting probed, scanned, tcp/udp malicious data packets, etc... I setup a sensor so I could figure out where all this shit is coming from and get an idea how consistant it is. Has anyone else noticed the nodes are exposed to all sorts of attack traffic? IS any of the data I log useful to
19:32:16 <agentpatience> the devs?
19:34:30 <agentpatience> IS there anyway the node can become hostile to bad traffic and just shitlist it? Is this better done at IPS appliance?
19:46:56 <moneromooo> It's normal to get random cunts probe. You can ignore, it's background noise.
22:18:16 <monerofanboy> "Hi Guys, Since I have been operating full node I m seeing a lot of bad behaviouron the network, i'm getting probed, scanned, tcp/udp malicious data packets, etc."
22:18:16 <monerofanboy> People are always probing on the internet. If you can, close unused ports and restrict traffic to only tcp on the needed ports using your firewall, at least for your Monero node. When running a webserver like Apache2, if you add ModSecurity, the
22:18:16 <monerofanboy> OWASP Core Rules and use fail2ban, fail2ban will constantly be banning bots which are probing the webserver.
22:18:17 <monerofanboy> Port/protocal restrictions do help to secure nodes. If you wanted to put Snort or Suricata in front of your node, I doubt it would hurt, but I also do not know that it would significantly increase your node's security, if you regularly install patches for the node's OS.