09:32:14 <m-relay> <d​igoutpr:matrix.org> Get in touch with this platform for greatness you’ll definitely thank me later       
09:32:15 <m-relay> <d​igoutpr:matrix.org> ℹ️❤️.  👇👇
09:32:17 <m-relay> <d​igoutpr:matrix.org>      
09:32:19 <m-relay> <d​igoutpr:matrix.org> https://t.me/+js75vxeR0MxiODQx
09:40:28 <m-relay> <d​igoutpr:matrix.org> Get in touch with this platform for greatness you’ll definitely thank me later       
09:40:29 <m-relay> <d​igoutpr:matrix.org> ℹ️❤️.  👇👇
09:40:31 <m-relay> <d​igoutpr:matrix.org>      
09:40:33 <m-relay> <d​igoutpr:matrix.org> https://t.me/+js75vxeR0MxiODQx
09:41:17 <m-relay> <s​yntheticbird:monero.social> monerobull plowsof
13:54:10 <m-relay> <s​gp_:monero.social> I've begun looking for potential auditors of the helioselene library
14:01:08 <m-relay> <s​gp_:monero.social> The main review tasks as I understand them are:
14:01:09 <m-relay> <s​gp_:monero.social> 1. Address the code question on divisors that kayaba mentioned in the meeting
14:01:11 <m-relay> <s​gp_:monero.social> 2. Helioselene library review (formal verification?)
14:01:13 <m-relay> <s​gp_:monero.social> 3. Formalization + proving for multisig protocol
14:01:15 <m-relay> <s​gp_:monero.social> 4. Regular + multisig GSP implementation review
14:01:17 <m-relay> <s​gp_:monero.social> 5. Optional: divisors library review (a bug is much less damaging in practice)
14:01:19 <m-relay> <s​gp_:monero.social> 6. Optional: Additional divisors cryptography and implementation review
15:22:04 <m-relay> <r​avfx:xmr.mx> LIONLINK (from the MRL banlist) also operate a crapton of **i2p** spynodes.
15:22:05 <m-relay> <r​avfx:xmr.mx> If you guys have monero nodes with i2p support, I think the MRL banlist should be applied with iptables
15:22:07 <m-relay> <r​avfx:xmr.mx> ```
15:22:09 <m-relay> <r​avfx:xmr.mx> ipset create MRL_Ban_list_net hash:net
15:22:11 <m-relay> <r​avfx:xmr.mx> ipset create MRL_Ban_list_ip hash:ip
15:22:13 <m-relay> <r​avfx:xmr.mx> Split the banlist into two file (one with the subnets and one with the ips)
15:22:15 <m-relay> <r​avfx:xmr.mx> while IFS= read -r line; do
15:22:17 <m-relay> <r​avfx:xmr.mx>     if [[ $line ]]; then  # Skip empty lines
15:22:19 <m-relay> <r​avfx:xmr.mx>         ipset add MRL_Ban_list_net "$line"
15:22:21 <m-relay> <r​avfx:xmr.mx>     fi
15:22:23 <m-relay> <r​avfx:xmr.mx> done < /etc/fuckoffnet.txt
15:22:59 <m-relay> <s​yntheticbird:monero.social> cc boog900
15:23:00 <m-relay> <r​avfx:xmr.mx> Then a few minutes later one can run iptables -L -n -v | grep MRL_Ban_list_net
15:23:52 <m-relay> <r​avfx:xmr.mx> Should look like that if it work. First digits is the amount of blocked packets, second one is the amount of blocked bytes
15:23:53 <m-relay> <r​avfx:xmr.mx> https://matrix.monero.social/_matrix/media/v1/download/xmr.mx/LYaIbbpJIOqxrqQdCsGIZOzR
15:26:14 <m-relay> <r​ucknium:monero.social> According to https://linkinglion.net/ , you should report that to network_abuse⊙ln .
15:26:15 <m-relay> <r​ucknium:monero.social> (This is a joke).
15:26:48 <m-relay> <r​ucknium:monero.social> RavFX: Thank you for investigating this. Very interesting 👀
15:27:16 <m-relay> <r​avfx:xmr.mx> I totally found that unexpected
15:27:17 <m-relay> <r​avfx:xmr.mx> Was playing with portmaster 😂
15:27:19 <m-relay> <r​ucknium:monero.social> ^ AFAIK, that is a real press release from LionLink
15:27:53 <m-relay> <r​avfx:xmr.mx> Ended up blocking there ASN too
15:32:22 <m-relay> <b​oog900:monero.social> Also Tor nodes: https://metrics.torproject.org/rs.html#search/as:54098
15:33:05 <m-relay> <b​oog900:monero.social> Some of the names are interesting
15:34:43 <m-relay> <r​avfx:xmr.mx> Sus, 
15:34:45 <m-relay> <r​avfx:xmr.mx> I just added 23.92.
15:34:52 <m-relay> <r​avfx:xmr.mx> 23.92.34.0/24 to my list
15:41:00 <m-relay> <r​avfx:xmr.mx> Also add theses for the output chain
15:41:01 <m-relay> <r​avfx:xmr.mx> ```
15:41:03 <m-relay> <r​avfx:xmr.mx> iptables -A OUTPUT -m set --match-set MRL_Ban_list_net dst -j DROP
15:41:05 <m-relay> <r​avfx:xmr.mx> iptables -A OUTPUT -m set --match-set MRL_Ban_list_ip dst -j DROP
15:41:07 <m-relay> <r​avfx:xmr.mx> ```
15:41:09 <m-relay> <r​avfx:xmr.mx> so it's properly blocked both way (will edit me previous paste with that)
15:41:24 <m-relay> <r​avfx:xmr.mx> LIONLINK (from the MRL banlist) also operate a crapton of **i2p** spynodes.
15:41:25 <m-relay> <r​avfx:xmr.mx> If you guys have monero nodes with i2p support, I think the MRL banlist should be applied with iptables
15:41:27 <m-relay> <r​avfx:xmr.mx> ```
15:41:29 <m-relay> <r​avfx:xmr.mx> ipset create MRL_Ban_list_net hash:net
15:41:31 <m-relay> <r​avfx:xmr.mx> ipset create MRL_Ban_list_ip hash:ip
15:41:33 <m-relay> <r​avfx:xmr.mx> Split the banlist into two file (one with the subnets and one with the ips)
15:41:35 <m-relay> <r​avfx:xmr.mx> while IFS= read -r line; do
15:41:37 <m-relay> <r​avfx:xmr.mx>     if [[ $line ]]; then  # Skip empty lines
15:41:39 <m-relay> <r​avfx:xmr.mx>         ipset add MRL_Ban_list_net "$line"
15:41:41 <m-relay> <r​avfx:xmr.mx>     fi
15:41:43 <m-relay> <r​avfx:xmr.mx> done < /etc/fuckoffnet.txt
15:43:38 <m-relay> <r​ucknium:monero.social> Must be the most suspicious ASN in the world right now. Spying on Monero, BTC, Tor, and I2P.
23:19:54 <m-relay> <g​ingeropolous:monero.social> what does an i2p spynode do
23:33:30 <m-relay> <v​tnerd:monero.social> Worse case they catch two txes over the same circuit, which basically links the txes. Otherwise, spying would likely have to be done at the isp level to correlate all traffic or something
23:34:15 <m-relay> <v​tnerd:monero.social> *links the txes to the same sender. But even then it doesn't leak ip without additional info
23:35:04 <m-relay> <v​tnerd:monero.social> Or there's a data leak over the p2p protocol we need fixing, maybe they know something we dont yet
23:35:22 <m-relay> <r​avfx:xmr.mx> What if they modified there nodes
23:35:23 <m-relay> <r​avfx:xmr.mx> Can all there i2p connect together to form circuit?
23:35:53 <m-relay> <r​avfx:xmr.mx> In a way that would allow them to get the "in" and "out" of a circuit (if you enter by one of there spynode)?
23:36:07 <m-relay> <r​avfx:xmr.mx> Bonus point if you connect to one of there spy monero or bitcoin node
23:37:07 <m-relay> <r​avfx:xmr.mx> Each of there i2p spy IP seam to have 10 nodes