<d​igoutpr:matrix.org> Get in touch with this platform for greatness you’ll definitely thank me later

<d​igoutpr:matrix.org> ℹ️❤️. 👇👇

<d​igoutpr:matrix.org>

<d​igoutpr:matrix.org> t.me/+js75vxeR0MxiODQx

<d​igoutpr:matrix.org> Get in touch with this platform for greatness you’ll definitely thank me later

<d​igoutpr:matrix.org> ℹ️❤️. 👇👇

<d​igoutpr:matrix.org>

<d​igoutpr:matrix.org> t.me/+js75vxeR0MxiODQx

<s​yntheticbird:monero.social> monerobull plowsof

<s​gp_:monero.social> I've begun looking for potential auditors of the helioselene library

<s​gp_:monero.social> The main review tasks as I understand them are:

<s​gp_:monero.social> 1. Address the code question on divisors that kayaba mentioned in the meeting

<s​gp_:monero.social> 2. Helioselene library review (formal verification?)

<s​gp_:monero.social> 3. Formalization + proving for multisig protocol

<s​gp_:monero.social> 4. Regular + multisig GSP implementation review

<s​gp_:monero.social> 5. Optional: divisors library review (a bug is much less damaging in practice)

<s​gp_:monero.social> 6. Optional: Additional divisors cryptography and implementation review

<r​avfx:xmr.mx> LIONLINK (from the MRL banlist) also operate a crapton of **i2p** spynodes.

<r​avfx:xmr.mx> If you guys have monero nodes with i2p support, I think the MRL banlist should be applied with iptables

<r​avfx:xmr.mx> ```

<r​avfx:xmr.mx> ipset create MRL_Ban_list_net hash:net

<r​avfx:xmr.mx> ipset create MRL_Ban_list_ip hash:ip

<r​avfx:xmr.mx> Split the banlist into two file (one with the subnets and one with the ips)

<r​avfx:xmr.mx> while IFS= read -r line; do

<r​avfx:xmr.mx> if [[ $line ]]; then # Skip empty lines

<r​avfx:xmr.mx> ipset add MRL_Ban_list_net "$line"

<r​avfx:xmr.mx> fi

<r​avfx:xmr.mx> done < /etc/fuckoffnet.txt

<s​yntheticbird:monero.social> cc boog900

<r​avfx:xmr.mx> Then a few minutes later one can run iptables -L -n -v | grep MRL_Ban_list_net

<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

<r​avfx:xmr.mx> matrix.monero.social/_matrix/media/…oad/xmr.mx/LYaIbbpJIOqxrqQdCsGIZOzR

<r​ucknium:monero.social> According to linkinglion.net , you should report that to network_abuse⊙ln .

<r​ucknium:monero.social> (This is a joke).

<r​ucknium:monero.social> RavFX: Thank you for investigating this. Very interesting 👀

<r​avfx:xmr.mx> I totally found that unexpected

<r​avfx:xmr.mx> Was playing with portmaster 😂

<r​ucknium:monero.social> ^ AFAIK, that is a real press release from LionLink

<r​avfx:xmr.mx> Ended up blocking there ASN too

<b​oog900:monero.social> Also Tor nodes: metrics.torproject.org/rs.html#search/as:54098

<b​oog900:monero.social> Some of the names are interesting

<r​avfx:xmr.mx> Sus,

<r​avfx:xmr.mx> I just added 23.92.

<r​avfx:xmr.mx> 23.92.34.0/24 to my list

<r​avfx:xmr.mx> Also add theses for the output chain

<r​avfx:xmr.mx> ```

<r​avfx:xmr.mx> iptables -A OUTPUT -m set --match-set MRL_Ban_list_net dst -j DROP

<r​avfx:xmr.mx> iptables -A OUTPUT -m set --match-set MRL_Ban_list_ip dst -j DROP

<r​avfx:xmr.mx> ```

<r​avfx:xmr.mx> so it's properly blocked both way (will edit me previous paste with that)

<r​avfx:xmr.mx> LIONLINK (from the MRL banlist) also operate a crapton of **i2p** spynodes.

<r​avfx:xmr.mx> If you guys have monero nodes with i2p support, I think the MRL banlist should be applied with iptables

<r​avfx:xmr.mx> ```

<r​avfx:xmr.mx> ipset create MRL_Ban_list_net hash:net

<r​avfx:xmr.mx> ipset create MRL_Ban_list_ip hash:ip

<r​avfx:xmr.mx> Split the banlist into two file (one with the subnets and one with the ips)

<r​avfx:xmr.mx> while IFS= read -r line; do

<r​avfx:xmr.mx> if [[ $line ]]; then # Skip empty lines

<r​avfx:xmr.mx> ipset add MRL_Ban_list_net "$line"

<r​avfx:xmr.mx> fi

<r​avfx:xmr.mx> done < /etc/fuckoffnet.txt

<r​ucknium:monero.social> Must be the most suspicious ASN in the world right now. Spying on Monero, BTC, Tor, and I2P.

<g​ingeropolous:monero.social> what does an i2p spynode do

<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

<v​tnerd:monero.social> *links the txes to the same sender. But even then it doesn't leak ip without additional info

<v​tnerd:monero.social> Or there's a data leak over the p2p protocol we need fixing, maybe they know something we dont yet

<r​avfx:xmr.mx> What if they modified there nodes

<r​avfx:xmr.mx> Can all there i2p connect together to form circuit?

<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)?

<r​avfx:xmr.mx> Bonus point if you connect to one of there spy monero or bitcoin node

<r​avfx:xmr.mx> Each of there i2p spy IP seam to have 10 nodes