SNeedlewoods opened pull request #10379: fix: return early in sensitive methods for --restricted-rpc [release-v...

> monero-project/monero #10379

SNeedlewoods opened pull request #10378: fix: return early in sensitive methods for --restricted-rpc

> monero-project/monero #10378

<s​hortwavesurfer2009:monero.social> Forgive me if this is the wrong place for this, but I figure I should bring this up to the core team.

<s​hortwavesurfer2009:monero.social> I am currently on a 256kbps (~32KB/s) cellular data connection and am unable to sync my wallet.

<s​hortwavesurfer2009:monero.social> Ofrnxmr said that the node i connect to needs to have `--disable-rpc-ban` flag. However, this is not default, and so the vast majority of public nodes are unusable on a very common throttle speed.

<o​frnxmr:xmr.mx> I doubt 32KB/s is a common throttle speed

<o​frnxmr:xmr.mx> I2P can get down to like 150KB/s and will syill sync

<s​hortwavesurfer2009:monero.social> It really is though. A lot of data plans will give you a certain amount of high-speed data and then throttle you to 256 kbps.

<s​hortwavesurfer2009:monero.social> It really is though. A lot of data plans will give you a certain amount of high-speed data and then throttle you to 256 kbps.

you can assume that any tor node has disable-rpc-ban, otherwise they ban localhost (everyone) if one client misbehaves. have you confirmed using a remote node with disable rpc ban works for you?

<s​hortwavesurfer2009:monero.social> I tried rucknium onion and plowsof onion with no success

<s​hortwavesurfer2009:monero.social> Normally, I connect my wallet to my own node over Tor and hadn't actually had the disable flag set myself.

<s​hortwavesurfer2009:monero.social> I never even realized I needed to set it for a tour node and have been using it all this time for over a year without that.

<o​frnxmr:xmr.mx> Youre using extra bandwidth by being connected to tor

<s​hortwavesurfer2009:monero.social> I'm not certain if my reply directly to the relay bot came through it or not on IRC, so I'll say it without being in a reply that I used rucknium onion and plowsof onion and it still would not sync

<o​frnxmr:xmr.mx> Try a clearnet endpoint for one of plowsof nodes

<s​hortwavesurfer2009:monero.social> If either of those have --disable-rpc-ban i am not sure

<o​frnxmr:xmr.mx> I mentioned on simplex that your messages are not being related to all simplex servers in your current situation, so youve probably oversaturated your bandwidth

node3.monerodevs.org:18089 node2.monerodevs.org:18089 node.monerodevs.org:18089

<o​frnxmr:xmr.mx> Youre running monerod, simplex, and trying to sync a wallet at the same time. I wouldnt expect good results from any of those data-hogs

<o​frnxmr:xmr.mx> You have 32KB/s available across all 3

<s​hortwavesurfer2009:monero.social> Wallet and simplex are on phone. Monerod is on desktop connected to wifi which currently has no internet.

<s​hortwavesurfer2009:monero.social> In order to test Monero D, I have to use my phone's hotspot and connect it to my router via ethernet.

<o​frnxmr:xmr.mx> shut down simplex and invizible / tor and try one of the linked nodes

<s​hortwavesurfer2009:monero.social> Will try monerodevs node and see if it syncs

<j​pk68:matrix.org> Sorry, I don't mean to bury this conversation

<j​pk68:matrix.org> Not really sure if it's an issue on my end, but building fails on v0.18.4.6 with clang++

<j​pk68:matrix.org> I can't find any issues about this

<o​frnxmr:xmr.mx> Does 18.4.5 build?

<j​pk68:matrix.org> Trying now

<j​pk68:matrix.org> Yes, it also fails

<s​hortwavesurfer2009:monero.social> If it works without Tor, that's still a problem IMO bc it means exposing ip address and not being able to connect to my own personal node when on the go

<j​pk68:matrix.org> Yes, it also fails (on obj_rpc)

<o​frnxmr:xmr.mx> Upload build error to a paste

<j​pk68:matrix.org> Will do

<j​pk68:matrix.org> ofrnxmr paste.debian.net/hidden/a474a425

<j​pk68:matrix.org> The issue on 18.4.5 (in pastebin) is not the same as the one I mentioned previously; that one was pretty unclear

<j​pk68:matrix.org> It also failed on obj_rpc instead

<o​frnxmr:xmr.mx> monero-project/monero #10280

<o​frnxmr:xmr.mx> Does master fail?

<s​hortwavesurfer2009:monero.social> Node.monerodevs.org:18089 didnt work clearnet to clearnet

<o​frnxmr:xmr.mx> Define "didnt work". Did it disconnect after attempting to sync for a while?

<s​hortwavesurfer2009:monero.social> Yes

<v​tnerd:monero.social> I never applied to 0.18 branch as it appeared to work. Possible I missed it. I'll try to post to 0.18

<o​frnxmr:xmr.mx> the opposite - your pr is to releqse

<o​frnxmr:xmr.mx> Master is what worked

<o​frnxmr:xmr.mx> Try a different wallet program (monero.com, monero-wallet-cli etc)

<j​pk68:matrix.org> Thanks. FWIW I encountered this after trying to build the GUI with clazy (KDE's clang++ wrapper for Qt lints)

<s​hortwavesurfer2009:monero.social> Will do

<j​pk68:matrix.org> It looks like vtnerd's fix worked

<j​pk68:matrix.org> I'll just manually update the submodule. Thanks for your help :)

<o​frnxmr:xmr.mx> Which fix?

<o​frnxmr:xmr.mx> Master always worked, it was release that was broken ^

<s​hortwavesurfer2009:monero.social> I will continue testing this later when I have my Wi-Fi back as Monero.com is 124 megabytes and that is going to take an incredibly long time to download at 32KB/s

<j​pk68:matrix.org> Yes, that's what I mean

<j​pk68:matrix.org> Master works for me, but not release