00:49:02 <TrasherDK[m]> Building master on Slackware x64 14.2 failed
00:49:03 <TrasherDK[m]> https://paste.debian.net/1246323
00:59:23 <TrasherDK[m]> Slackware x64 15.0 is fine tho.
00:59:41 <TrasherDK[m]> $ monerod --version
00:59:41 <TrasherDK[m]> Monero 'Oxygen Orion' (v0.17.0.0-b54d5ae38)
01:08:30 <selsta> TrasherDK[m]: which ubuntu version?
01:08:39 <selsta> sorry i meant which openssl version
01:08:54 <selsta> on 14.2
01:09:20 <selsta> MeowingCat: that's why i recommended to run make depends directly
01:09:39 <TrasherDK[m]> # openssl version
01:09:39 <TrasherDK[m]> OpenSSL 1.0.2u  20 Dec 2019
01:09:53 <selsta> seems ancient?
01:10:17 <selsta> is it possible to update?
01:10:41 <TrasherDK[m]> Well, 14.2 is ancient, but rock solid.
01:12:08 <TrasherDK[m]> Updates are only possible if I want to maintain the packages myself, unless I can point cmake to "local" version.
01:12:43 <selsta> we added openssl 3.0 support and seems as a consequence old openssl broke
01:12:55 <selsta> openssl 1.1.x should be recent enough
01:13:54 <TrasherDK[m]> Even the dev branch "current" is at OpenSSL 1.1.1q  5 Jul 2022
01:14:12 <selsta> you can tell `cmake -D OPENSSL_ROOT_DIR=`
01:14:30 <selsta> yes, you need at least 1.1.x or 3.0
01:17:28 <TrasherDK[m]> Okay. So I need to make a static build of openssl and do a install DESTDIR=$somewhere_local
01:18:08 <selsta> should work
01:18:44 <TrasherDK[m]> Cool. I'll try. Thanks.
02:05:40 <hyc> MeowingCat: yeah, what selsta said. just do "make depends target=aarch64-linux-android"
03:09:37 <selsta> ofrnxmr[m]: was it you that had the difficulty drift bug? can you compile my latest master-beta branch and see if you can still reproduce it?
03:25:56 <ofrnxmr[m]> selsta: 
03:25:56 <ofrnxmr[m]> This one?
03:25:56 <ofrnxmr[m]> https://libera.monerologs.net/monero-dev/20220622#c111934
03:25:56 <ofrnxmr[m]>  I'm not sure why it happened, and have only seen it once. But yeah, will update to the latest and keep logs
03:26:20 <selsta> yes this one
03:27:01 <selsta> i think it doesn't show up anymore with the latest version, or maybe i just had bad luck and have to wait longer until i trigger it
03:30:03 <selsta> .merge+ 8394
03:30:03 <xmr-pr> Added
04:57:10 <luigi1111w> .merges
04:57:10 -xmr-pr- 8371 8388 8390 8391 8394 8400 8404 8408 8412 8413 8414
05:03:50 <luigi1111w> gonna leave 8414 until branch is pending
06:42:15 <TrasherDK[m]> Soo, I guess I'll also need a local static build of boost.
06:42:17 <TrasherDK[m]> Boost 105900 (older than 1.62) is too old to link with OpenSSL 1.1.1q
09:24:56 <moneroextremist[> Seth For Privacy: Check DMs.
13:22:33 <welcomeworld[m]> based on recent comments regards tor setup i made a pull request. https://github.com/monero-project/monero/pull/8423
13:59:16 <moneromooo> Thanks, always welcome.
15:03:55 <TrasherDK[m]> Did someone update the docs, saying ssl below 1.1.1 and a boost that ssl 1.1.1 is happy with, is required for running this thing, leaving behind a shitload of peeps, not running the latest ubuntu/debian ? Who the fuck decided that ssl 3.x was the way to go?
15:09:45 <moneromooo> Did you check the commit message ?
15:11:56 <TrasherDK[m]> Eh, git pull origin? No, witch one?
15:15:30 <moneromooo> I mean the message in the commit that added openssl 3.x support and/or removed older ones.
15:15:37 <moneromooo> It might explain the rationale.
15:17:26 <TrasherDK[m]> I'm getting issues/pr's, but have missed something. Clues, please. # would help.
15:23:12 <moneromooo> You can grep as fast as I can :)
15:23:32 <moneromooo> I wasn't saying "the commit message explains", but really "it might".
15:59:14 <TrasherDK[m]> I have no clue how to grep a commit message. Using `git log -p --name-only --grep=openssl | less`, searching for '3\.` is not helpful. "ssl: server-side: allow multiple version of TLS" and iOS something. Sorry Moo, I'm a git illiterate. Basic stuff I know.
16:14:10 <moneromooo> I usualy just "git log", then /[Oo]pen[sS]
16:14:37 <moneromooo> or, if I know where in a file part of the change is, git blame $thatfile
16:14:56 <moneromooo> Then git blame $thatfile irrelevantcommit^ till I find a good one.
16:42:14 <TrasherDK[m]> The last commit, after my last successful build, is :
16:42:16 <TrasherDK[m]> commit 9750e1fa103539b3e533455500610aae76e253a5... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/e68889478e3abe5512e42f52e38ccf492753c4d6)
16:42:19 <selsta> TrasherDK[m]: Ubuntu 18.04 has a new enough OpenSSL
16:42:29 <selsta> what distro are you running?
16:42:43 <selsta> and is it a good idea to use outdated openssl?
16:43:45 <TrasherDK[m]> Yeah, I guess. My servers are running Slackware 14.2/15.0 The Monero ones are still on 14.2
16:45:16 <TrasherDK[m]> Vulnerable versions of openssl are patched and released within 1 day.
16:47:28 <TrasherDK[m]> I seems that openssl 1.1.0 and 1.1.1 need more patching than 1.0.x versions.
16:49:04 <selsta> https://www.openssl.org/policies/releasestrat.html
16:49:12 <selsta> Version 1.1.1 will be supported until 2023-09-11 (LTS).
16:51:03 <selsta> Version 1.0.2 is no longer supported. Extended support for 1.0.2 to gain access to security fixes for that version is available.
16:56:10 <TrasherDK[m]> I don't think the Slackware guys care too much. They are still pushing updates to 1.0x when required. Latest was `Jun 29 10:32` version `openssl-1.0.2u-x86_64-4_slack14.2`
16:59:05 <selsta> yes, that's from 2019
17:02:16 <TrasherDK[m]> If that was the case, the date would have a year. Most of the vulnerabilities discovered are in the recent releases.
17:04:58 <TrasherDK[m]> Those versions released by the Slackware team, are not just flat copies of the upstream. They are often patched beyond the source.
17:05:33 <hyc> that's kind of worrisome. who's writing their patches? could be like debian and introduce new vulns
17:06:01 <hyc> IMO, while OpenSSL 3.0's API kinda sucks, we should be migrating to it since 1.1.1 will be dead soon
17:19:47 <TrasherDK[m]> Well.. My mainnet, testnet and stagenet are running with openssl `1.0.2u`. All the certificates, connection my network, same. All are TLS 1.2 (I think) I upgraded 5+ hosts to v15.0, and that was a bitch. Doing it to 10+ more kinda turns me off. Anyway. If I can build static dependencies, and build the Monero binaries as static, I will keep the nodes running.
17:23:12 <TrasherDK[m]> Anyone got a bash script to build boost as static, I'm interested 🙂 
17:23:37 <hyc> "make depends" builds all dependencies as static
17:25:27 <selsta> make depends target=x86_64-linux-gnu
17:26:23 <selsta> don't know if it works on your slackware version, we tested it on ubuntu 18.04 and 20.04
17:26:33 <selsta> that's how we build boost https://github.com/monero-project/monero/blob/master/contrib/depends/packages/boost.mk
17:28:40 <TrasherDK[m]> So far it doesn't look too promising: `Failed to connect to samba.org port 443 after 15221 ms`
17:29:17 <TrasherDK[m]> Ah, now it's going.
17:36:10 <TrasherDK[m]> So I should probably get rid of `-DBOOST_IGNORE_SYSTEM_PATHS=OFF` when building, right?
17:37:39 <TrasherDK[m]> Will `cmake bla bla ${path_to_source}` do the trick?
17:38:00 <selsta> where did you add this?
17:41:49 <TrasherDK[m]> I have `./build` and `./source`. In `./build` I do `cmake -DCMAKE_BUILD_TYPE=static -D OPENSSL_ROOT_DIR=${openssl} ../source`.  This is after the `make depends` in `./source`
17:42:31 <TrasherDK[m]> `make depends` are still grinding.
17:50:08 <selsta> is this a separate question in case make depends doesn't work?
17:54:55 <selsta> otherwise i'm not sure what you are trying to do
17:56:00 <TrasherDK[m]> `make depends` didn't work. boost failed:
17:57:49 <TrasherDK[m]> `CMake Warning at /usr/share/cmake-3.5/Modules/FindBoost.cmake:725 (message):... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/7bf44e4ac68d6d8229e6bf58644a37d64b9bfccc)
18:02:44 <TrasherDK[m]> I'm at zulu+7, I have to drop off. I'll look at doing a static boost, when I wake up 😴
18:40:22 <selsta> you can always use docker to build static binaries
18:41:03 <selsta> https://github.com/monero-project/monero/blob/master/contrib/gitian/DOCKRUN.md
21:22:41 <selsta> soo I updated my OS and now everything seems broken in monero, here is an example backtrace for `monerod`: https://paste.debian.net/hidden/f210ba9f/
21:22:59 <selsta> thread 9 doesn't even display anything so no idea what this is
21:23:14 <selsta> this was with a release build, with a debug build i can't reproduce the crash but monerod doesn't sync any blocks
21:23:34 <selsta> the only other thing i can try is if my db is corrupted for some reason
21:26:01 <sech1> the crashed thread doesn't show any callstack, and all other threads are either blocke waiting or also with no callstack
21:26:42 <selsta> i deleted my db and it starts to sync again, but no idea how it got corrupted in the first place
21:31:17 <selsta> seems like both of my issues were broken wallet cache and broken db
21:31:30 <selsta> hopefully my SSD isn't broken lol
22:31:30 <selsta> we don't use lmdb for the wallet cache, right?
22:39:14 <selsta> this wallet use after free issue is remaining: https://paste.debian.net/hidden/e6ee8b39/
22:39:19 <selsta> any tips on how to debug this?
23:13:54 <hyc> right, wallet cache is just a plain file
23:14:02 <hyc> sounds like your ssd is flaky
23:22:21 <selsta> hyc: which macos version do you have on your m1 macbook?
23:23:22 <selsta> the ssd is like half a year old so i would be really surprised if that's the issue, i can consistently reproduce the use after free during wallet scanning