03:28:21 <winircuser-980> a
10:08:47 <normo> \quit
11:39:09 <Kronovestan> selsta, new host my system auto blocked 100.19.74.83
11:41:14 <selsta> auto block can have many reasons, I would prefer to only add IPs that are confirmed to do the +2 attack
11:41:30 <Kronovestan> gotcha
11:49:56 <selsta> Kronovestan: when was this ban?
11:56:34 <selsta> also which version are you running?
15:21:39 <Kronovestan> selsta, the ban here https://i.imgur.com/FI92PGS.png
17:17:47 <gingeropolous> is there a way to just restart the rpc server?
17:18:42 <moneromooo> Send it signal 15, start it again.
17:20:31 <gingeropolous> lulz. naw, i mean within monerod itself. I see during monerod boot up it says" rpc server initialized OK". I'd like to maintain my p2p connections etc, but just restart rpc.
17:21:29 <moneromooo> It us unclear what that means. Closing the port and reopening it maybe ?
17:22:53 <gingeropolous> i dunno. all i know is after a while, my high load public remote node can't get more wallet connections. restarting monerod "fixes" it. just wondering if there's an even hackier solution.
17:23:39 <moneromooo> Do you have error messages ? If so, which ones ? Do you have loads of entries in /proc/`pidof monerod`/fd ?
19:23:52 <binaryFate> v0.17.1.7 binaries are now available at https://www.getmonero.org/downloads
19:36:27 <Lyza> cheers
19:39:02 <Inge-> 1
19:42:43 <sech1> Running 0.17.1.7 without block list and out-peers=64, let's see how it goes
19:59:06 <Kronovestan> sech1, what's the command you do to start it with out-peers
20:35:55 <sech1> Kronovestan --out-peers 64
20:36:59 <hyc> or just type out_peers 64 at the monerod command prompt
20:48:14 <hyc> the 0.17.1.7 release notes should have mentioned that the upgrade of OpenSSL to 1.1.1i was because of their latest security advisory https://www.openssl.org/news/secadv/20201208.txt
20:48:48 <hyc> since monerod can optionally use TLS on a various connections, it was vulnerable to DoS attack thru this vector
20:49:26 <hyc> the release notes currently just mention the upgrade as if it was a routine change or just did it for no reason
20:49:40 <hyc> which is rather misleading...
20:58:10 <binaryFate> I can update them
21:02:47 <binaryFate> "Update OpenSSL to 1.1.1i to fix its recent [https://www.openssl.org/news/secadv/20201208.txt](vulnerability)" ?
21:02:55 <hyc> sounds good
21:12:59 <Kronovestan> once I incrase to outpeers 64 then the "bug" happens again where I'm off by 2 blocks ... (this is WITHOUT the ban list for testing purps and .7 release)
21:17:20 <selsta> Kronovestan: it takes a couple seconds to get the peer kicked
21:17:52 <selsta> stay at 12 out peers so that you connect to attacker nodes less often
21:18:03 <selsta> if you don't want to use the ban list
21:18:49 <dEBRUYNE> hyc, binaryFate: Will update the Reddit thread too
21:23:39 <hyc> cool
21:28:11 <binaryFate> dEBRUYNE you can use same phrasing as in https://www.getmonero.org/2020/12/13/monero-0.17.1.7-released.html
21:29:42 <Inge-> ok I'm getting differing hashes now, this is weird.
21:31:16 <Inge-> is  https://dlsrc.getmonero.org/cli/monero-linux-x64-v0.17.1.7.tar.bz2 the same file as https://downloads.getmonero.org/gui/linux64 ?
21:32:12 <dEBRUYNE> binaryFate: ty
21:32:20 <dEBRUYNE> Inge-: Should be, yes
21:32:24 <Inge-> used to be
21:33:00 <Inge-> the former comes in at ~80MB, the latter at ~121MB
21:33:07 <Inge-> the latter has the correct sha256sum
21:34:12 <selsta> caching
21:34:19 <selsta> try a private browser window
21:34:30 <selsta> this should get fixed at some point
21:34:40 <Inge-> this was wget and curl from the command line
21:35:05 <Inge-> wait hang on... could be me being an idiot
21:36:49 <Inge-> Mixed in CLI and GUI here, I think all is well. Still a bit twitchy since that time...
21:59:50 <moneromooo> Kronovestan: can you post a level 2 log of when that happens ? Ideally from a couple of minutes before it happens.
22:00:19 -xmr-pr- vtnerd opened pull request #7151: Fix byte_stream::put_n
22:00:20 -xmr-pr- > https://github.com/monero-project/monero/pull/7151
22:02:43 <selsta> v0.17.1.7 definitely works for me, +2 nodes get kicked after ~10 seconds
22:45:03 <selsta> luigi1111w: please upload binaries to github releases
22:45:10 <selsta> and also update hashes.txt.sig
22:49:34 <luigi1111w> plz check
22:52:21 <Kronovestan> moneromooo, of course I'd be happy to... let me make it write the log to a file first. then restart the daemon
22:54:54 <moneromooo> set_log 2
23:02:17 <selsta> Kronovestan: are you sure the +2 peers stay connected?
23:03:58 <selsta> luigi1111w: looks good