00:12:17 <Nausicaa> your paste is expired preland, but i know with i2pd, if you reuse the same b32 for more than one service, only the first created service will connect, if the client does not specify a destination port, or specifies the wrong port. so i would double check your wallet config
00:13:16 <m-relay> <p​reland:monero.social> Yea I forgot to post again, but ofrn figured it out pretty fast I think
00:13:39 <m-relay> <p​reland:monero.social> Haven’t tested yet but it *should* work
00:16:30 <Nausicaa> also java i2p has a bug where you cannot access your own service on the same host (http://zzz.i2p/topics/3669-cannot-reach-local-eepsite-on-2-8-0)
01:13:35 <m-relay> <t​erracotaburger:unredacted.org> hello
01:14:03 <m-relay> <t​erracotaburger:unredacted.org> can i contact an xmr dev in private, its very urgent
01:17:34 <m-relay> <j​effro256:monero.social> vulnerability report?
01:18:17 <m-relay> <t​erracotaburger:unredacted.org> no its now new if i understand
01:18:28 <m-relay> <t​erracotaburger:unredacted.org> not new
01:18:30 <m-relay> <h​itojin:hitoj.in> dundundun
01:19:45 <m-relay> <j​effro256:monero.social> What category of issue is it?
01:20:13 <m-relay> <t​erracotaburger:unredacted.org> security but it is to inform you of an urgent situation
01:21:06 <m-relay> <j​effro256:monero.social> Do you need help with a specific security incident or is it an issue which may apply to other people ?
01:21:27 <m-relay> <t​erracotaburger:unredacted.org> this apply to other people
01:21:37 <m-relay> <t​erracotaburger:unredacted.org> and maybe everyone
01:21:52 <m-relay> <j​effro256:monero.social> Then I would submit a report at https://hackerone.com/monero?type=team
01:22:18 <m-relay> <j​effro256:monero.social> That's the "official" outlet
01:22:27 <plowsof> "but i am not reporting a vulnerability, it's linked to one"
01:24:03 <m-relay> <t​erracotaburger:unredacted.org> i want to share private conversations, i dont think hackerone is for that
01:26:48 <m-relay> <j​effro256:monero.social> Hmm is it like an instance of evidence of someone exploiting a vulnerability in the wild?
01:26:49 <m-relay> <t​erracotaburger:unredacted.org> yes
01:28:08 <m-relay> <j​effro256:monero.social> Is it DoS related, network privacy related, consensus protocol related, or something else?
01:28:27 <m-relay> <t​erracotaburger:unredacted.org> DoS related
01:30:13 <m-relay> <s​yntheticbird:monero.social> mamma mia
01:32:06 <m-relay> <j​effro256:monero.social> @selsta @vtnerd @boog900 tobtoht  would you be okay with me taking this issue?
01:33:04 <m-relay> <b​oog900:monero.social> fine with me
01:33:34 <m-relay> <j​effro256:monero.social> I don't want to volunteer y'all if you don't want it
01:34:39 <m-relay> <b​oog900:monero.social> sounds like the issue is already known this is just a report of a bad actor, right?
01:35:05 <m-relay> <j​effro256:monero.social> That's the impression I have
01:35:12 <m-relay> <v​tnerd:monero.social> Yikes. boog900: thats what I got out of the messages
01:38:19 <m-relay> <v​tnerd:monero.social> And yes, jeffro256: take whatever needs to be done
01:38:25 <m-relay> <j​effro256:monero.social> terracotaburger: you can DM me on Matrix and optionally encrypt to my PGP key: https://github.com/monero-project/monero/blob/master/utils/gpg_keys/jeffro256.asc (fingerprint 2EAAC930E6B90CB019C01E806F79797A6E392442). But @boog900 and @vtnerd are great options too
01:39:31 <m-relay> <v​tnerd:monero.social> Ah yes, I need to finish publishing my gpg key too
01:40:10 <m-relay> <t​erracotaburger:unredacted.org> idk how to use pgp i will message you jeffro256
03:21:43 <m-relay> <p​reland:monero.social> Guys the flood thing was funny one time we don’t need to make this an annual event /j
17:12:00 <selsta> .merges
17:12:00 -xmr-pr- 9456 9538 9654 9666 9671 9711 9727 9728 9729
17:24:01 <selsta> .merge+ 9792 9793 9790 9779 9778 9777 9773 9771 9770 9769 9763 9761 9762 9760 9759 9582 9717 9718 9687 9711
17:28:04 <selsta> .merge+ 8617
17:28:04 <xmr-pr> Added
17:46:54 <selsta> .merge+ 9722
17:46:54 <xmr-pr> Added
18:12:00 <tobtoht_> .merges
18:12:00 -xmr-pr- 9456 9538 9654 9666 9671 9727 9728 9729 9762 9773 9790
19:16:40 <ofrnxmr> .merges
19:16:40 -xmr-pr- 9456 9538 9654 9666 9671 9727 9728 9729 9762 9773
19:18:30 <SyntheticBird> .merges
19:18:30 -xmr-pr- 9456 9538 9654 9666 9671 9727 9728 9729 9762 9773
19:18:48 <SyntheticBird> .merge
19:18:53 <SyntheticBird> .help
19:18:53 <xmr-pr> lolnub
19:18:54 <hv-bridge> <Moss> I have the following commands: .effort Effort guide  .geo GEO DNS explained  .logs Logs guide  .pool-side-hash-rate Pool Hash rate reporting explanation  .ports Ports guide  .solo Solo guide  .вывод Вывод  .withdraw HashVault payment information  .xmrig XMRig Download links
19:19:39 <SyntheticBird> .xmrig
19:19:39 <hv-bridge> <Moss> Information about xmrig settings and options: https://xmrig.com/docs/miner For xmrig-proxy: https://xmrig.com/docs/proxy Performance Benchmarks: https://xmrig.com/benchmark  You can download XMRig from the following links: CPU+AMD+Nvidia: https://github.com/xmrig/xmrig/releases Proxy: https://github.com/xmrig/xmrig-proxy/releases For configuration examples follow the Getting Started page.
19:19:46 <SyntheticBird> this bot is fire
19:32:28 <m-relay> <r​ottenwheel:unredacted.org> The mergeathon keeps growing!
20:27:01 <ofrnxmr> .merges
20:27:01 -xmr-pr- 9538 9654 9666 9671 9727 9728 9729 9762 9773
20:27:17 <ofrnxmr> 9538 9654 9666 9671 9727 9728 9729 9762 9773
20:28:11 <m-relay> <o​frnxmr:xmr.mx> jeffro256 vtnerd  reviews where necessary plz
20:52:13 <selsta> .merge+ 9796
20:52:13 <xmr-pr> Added
21:00:05 -xmr-pr- iamamyth opened pull request #9796: tests: Improve p2p tx propagation functional test [v0.18]
21:00:05 -xmr-pr- > https://github.com/monero-project/monero/pull/9796