03:57:12 <Maxattax> if you buy monero on a kyc exchange, does that not just totally defeat the purpose of kyc?
03:57:35 <Maxattax> 1. join kyc exchange
03:57:43 <Maxattax> 2. buy xmr
03:57:53 <Maxattax> 3. transfer to wallet offsite
03:58:40 <Maxattax> 4. exchange xmr to anything else on another non-kyc exchange
03:59:00 <Maxattax> 5. call it a loss or say you bought something with the xmr
03:59:14 <Maxattax> 6. profit (untraceable monies?????)
04:20:42 <gingeropolous> naw, the bank, er exchange, did what they had to do.
04:22:10 <Maxattax> gingeropolous: they fulfilled kyc, but could the feds really come after you at that point?
04:23:55 <gingeropolous> i dunno. i never think its a wise idea to try and food the taxmen. unless of course your a billionaire, then you can do it with legal crap and make it too costly for them.
04:37:24 <bonedaddy> running monero-wallet-gui from the cli and letting it run eventually gives me an error `E Failed to fetch and verify signed hash: signature checksum doesn't match the expected value`
04:37:42 <bonedaddy> never seen this before, and i've used this version of monero-wallet-gui a number of times before
04:42:57 <selsta> bonedaddy: getmonero.org cert is expired, should be fixed in a couple hours
04:43:33 <bonedaddy> makes sense, thanks
04:43:57 <selsta> error should go away afterwards
04:43:59 <sixStringHobo> here i am looking it up and double checking to make sure before I posted about it
04:44:59 <sixStringHobo> https://pastebin.com/GV01QHKd
04:45:30 <sixStringHobo> thought someone trying something naughty
05:19:50 <shabash> my client keeps getting stuck on 2 daemon blocks remaining
05:20:03 <shabash> sometimes briefly going to 1 but then back to 2
05:20:14 <shabash> is it a problem with my computer/network?
05:25:26 <selsta> shabash: do you run your own daemon?
05:25:33 <selsta> also CLI or GUI?
05:25:45 <shabash> https://www.reddit.com/r/monerosupport/comments/jv3tub/monero_gui_stuck_at_2_daemon_blocks_remaining/
05:25:49 <shabash> no selsta
05:26:11 <shabash> GUI
05:26:33 <selsta> shabash: try one of the remote nodes from here https://github.com/monero-project/monero-gui/issues/3140#issuecomment-706440354
05:32:29 <shabash> sorry selsta I misinterpreted your first question
05:32:35 <shabash> yes I was running local node
05:33:21 <selsta> shabash: https://reddit.com/r/Monero/comments/kdqj5i/_/gfy1x01/?context=1
05:33:29 <selsta> follow this guide
05:42:41 <shabash> it does not connect to node.xmr.to
05:42:49 <shabash> does it need daemon username or password?
05:43:30 <shabash> I followed the "If you run Simple mode" instructions
05:44:01 <shabash> it just says network status connecting
05:52:22 <shabash> let me try another remote node
05:55:00 <selsta> 88.198.199.23:18081 works
05:56:54 <selsta> but you can just use your own guide by adding the ban list
05:57:02 <selsta> your own node*
06:09:22 <shabash> so far so good with the block list
06:11:32 <dgoddard__> I'm doing fine on 0.17.1.7 with selsta's banlist. One interesting IP got automatically blocked and unlocked
06:11:36 <dgoddard__> 2020-12-16 04:03:49.010	I Host 100.19.74.83 blocked.
06:11:44 <dgoddard__> 2020-12-17 04:38:47.814	I Host 100.19.74.83 unblocked.
06:11:46 <kloinka> MyI GUI wallet got stuck, updating my remote node fixed it.
06:12:16 <shabash> idk I couldn't connect to 2 different remote nodes
06:12:21 <shabash> maybe I wasn't doing something right
06:12:47 <selsta> no, looks like the issue were on the nodes side
06:13:07 <kloinka> Check version running on node?
06:14:08 <kloinka> I use my own remote node in-house 😎
06:31:44 <shabash> the new client on windows is very pretty
06:35:55 <shabash> thank you for maintaining the block list selsta
08:58:38 <scudyreal> All you are fighting for is e-penis of a guy you never met, that doesn't even have common decency to pay you for your time.
08:58:39 <scudyreal> Do you think they care about Monero, or privacy or anything other than money?
09:06:28 <fluffypony> jess: ^^
09:06:39 * jess rolls out of bed
09:06:45 <fluffypony> LOL apologies
09:07:05 <jess> no we need fireice to stop waking up before me
09:07:20 <p3rL> fluffypony wen xmr pump sir
09:07:44 <fluffypony> p3rL: never
09:07:52 <p3rL> then make it dump :D
09:08:03 <p3rL> xmriers wanna see something new
15:40:33 <Mochi101> fluffypony, I found the video of what was going on right before your boating accident: https://youtu.be/j--SsrgSF9I
15:43:17 <fluffypony> LOL
17:06:37 <dgoddard__> I'm guessing 45.140.176.144 is now on selsta's blocklist ;) fireice is now using IPs from Saudi Arabia telcom. I wonder if he's on that IP legally....
17:07:01 <selsta> is it on my block list?
17:07:12 <selsta> how did you get that IP?
17:07:33 <dgoddard__> It's the one that was used a few hours ago talking about epenises and BADCACA
17:07:49 <dgoddard__> "scudyreal"
17:07:57 <selsta> these are botnet IPs
17:08:01 <dgoddard__> ok
17:08:11 <selsta> I don’t bother adding as they don’t seem to be used for monero
17:08:15 <dgoddard__> :+1
17:09:32 <anchor[m]> this is why I hope blacklists aren't going to be the "fix"
17:09:41 <anchor[m]> it's just poor mitigation and turns into cat & mouse
17:09:52 <selsta> what is the alternative in the short term?
17:10:01 <selsta> we can’t get the whole network to update quickly
17:10:30 <anchor[m]> I'm no programmer or cryptographer but if it's this easy to attack the monero network I'm honestly baffled
17:10:54 <selsta> how do you know it is "easy"?
17:11:03 <anchor[m]> Because it's a child doing it
17:11:36 <selsta> we have a fix for it included in v0.17.1.7, but the majority of network has to update to it
17:11:38 <selsta> which will take a while
17:11:56 <anchor[m]> Didn't they say the same about .6?
17:12:12 <selsta> no
17:12:22 <selsta> .6 contained mitigations against the specific attack he was doing
17:12:27 <selsta> which he changed afterwards
17:12:29 <dgoddard__> A child can do SQL injection, you'd be surprised how many Fortune500 companies had their entire source code pwoned by Aurora
17:12:51 <anchor[m]> <selsta ".6 contained mitigations against"> I see
17:13:48 <selsta> the problem is a bit of information asymmetry, he can see what we are developing on github and has multiple days to find ways to circumvent it before we release
17:13:57 <selsta> we can’t see what he is preparing obviously
17:14:19 <moneromooo> People seem to get the wrong idea, which might be the point. The network's fine.
17:26:27 <selsta> yea, this is mostly a GUI specific DoS because the GUI expects the daemon to be synched before transacting
20:09:57 <dgoddard__> Running 0.17.1.17, did I find a new kind of Bad Node? 2020-12-17 17:10:05.919	I Host 159.89.121.89 blocked.
20:09:57 <dgoddard__> 2020-12-17 18:36:53.143	I [88.99.83.181:33204 INC] Sync data returned a new top block candidate: 2254342 -> 2254340 [Your node is 2 blocks (4.0 minutes) ahead]
20:09:57 <dgoddard__> 2020-12-17 18:36:53.143	I SYNCHRONIZATION started
20:09:57 <dgoddard__> 2020-12-17 19:44:49.380	W ge_frombytes_vartime failed at 415
20:10:15 <dgoddard__> IP not in selsta's list
20:15:52 <dgoddard__> How can I figure out which peer is saying the false blockheight?
20:16:01 <sethsimmons> sync_info
20:16:32 <dgoddard__> ty
20:21:15 <dgoddard__> I assume height 1 means "newly syncing"? I also see a few sort of randomly lower than I have, presumably that height being where they are at in the syncing process
20:24:53 <moneromooo> I think they're typically nodes that are set to not sync. Those should probably be dropped after a peer list is sent.
20:29:55 <dgoddard__> yep, they (those at height 1) drop off after peer list
20:29:57 <dgoddard__> ty