text
stringlengths
9
408
[584.62 --> 586.54] you have to use that are cloud-based.
[586.72 --> 588.26] There's no way around it sometimes.
[588.58 --> 590.88] And yeah, it does go out.
[591.22 --> 596.12] I have yet to have it cause an actual genuine issue.
[596.24 --> 598.44] For me, you know, it's an inconvenience, mostly.
[598.60 --> 600.86] Maybe a show goes out a couple hours later.
[600.86 --> 610.44] But in my IT life, I did have lawyers as clients, and there would often be like this extreme
[610.44 --> 614.22] time pressure to turn around a contract that has something to do with, you know, some $10
[614.22 --> 615.16] million deal.
[615.72 --> 619.30] And we did have a situation where the exchange server went down.
[620.16 --> 623.12] And it was like, red alert, all hands on deck.
[623.20 --> 624.92] Get this thing back up as fast as possible.
[625.00 --> 625.98] We've got to get this email up.
[625.98 --> 627.94] Because everybody self-hosted back then.
[628.62 --> 632.68] And so you can also sometimes have these outages when you self-host.
[632.94 --> 637.10] And, you know, I'm sure this has probably happened to everyone who's listening who's
[637.10 --> 638.04] self-hosted for a while.
[638.88 --> 641.30] It's going to fail when you're on vacation or something like that.
[641.54 --> 645.90] You know, like my server here at the studio, which had been running fantastic, of course,
[646.46 --> 648.46] crashed while I was on my road trip.
[648.56 --> 649.46] And I was stuck in Tucson.
[649.46 --> 652.64] And I couldn't get back here for a week to check on what was going on.
[653.12 --> 655.48] So that stuff happens when you self-host too.
[655.68 --> 657.40] And, you know, it's all on you to fix it.
[658.62 --> 662.94] Speaking of, I know I mentioned briefly that log4j vulnerability in the last bit.
[663.68 --> 667.92] The linuxserver.io team have posted an info notice.
[668.10 --> 672.92] I think this is a new thing they've started doing over at info.linuxserver.io about the
[672.92 --> 674.14] log4j vulnerability.
[674.14 --> 681.30] Essentially, this is a very critical vulnerability in Java, which leads to denial of service and
[681.30 --> 683.74] remote code execution in Java apps.
[684.56 --> 686.80] It's in Java version 11.
[686.96 --> 688.92] So it's quite a recent version of Java.
[689.86 --> 692.72] I think you and Wes did a full breakdown in this week's Land, didn't you?
[693.38 --> 697.36] Yeah, we got all the details in there and the steps you'd have to go through to actually
[697.36 --> 698.64] trigger the exploit.
[698.64 --> 704.20] But spoiler is, yeah, you could actually even get this thing to remotely connect to remote
[704.20 --> 706.48] URLs and pull down a shell script and run it.
[706.60 --> 707.64] So it's not good.
[707.72 --> 708.64] It's not good at all.
[709.12 --> 714.82] And ironically, it was found by Minecraft users who figured out they could take control of
[714.82 --> 721.10] the Minecraft server because most developers, and for totally reasonable reasons, are logging
[721.10 --> 724.96] the commands their users are entering into the shell so they know what the user was doing.
[724.96 --> 728.86] And if you take advantage of that, well, you could probably guess where that leads.
[729.32 --> 732.10] So there's a lot of Minecraft servers out there that people have set up for themselves
[732.10 --> 734.42] that are self-hosting that have to get updated.
[734.84 --> 735.56] And you know what?
[735.60 --> 739.56] I say good on Linux Server.io for going through and kind of letting people know what's up.
[739.88 --> 743.78] I think that's also pretty nice to see just because I use a lot of their containers.
[744.62 --> 748.16] The main one that stood out for me was the Unify controller as being vulnerable.
[748.74 --> 753.36] Obviously, that's got some pretty good network level access to your stuff.
[753.36 --> 756.30] And so if there's a vulnerability there, you want to be on top of it pretty quick.
[757.18 --> 761.36] There is a version released now with a workaround applied as well as an upstream fix.
[761.54 --> 766.22] So if you're running Unify from Linux Server in a container, go ahead and pull down that
[766.22 --> 766.48] update.
[766.58 --> 768.08] There's a few others on the web page as well.
[770.02 --> 775.00] Yeah, I know some of our listeners use Airsonic, and that's one that's currently vulnerable
[775.00 --> 775.50] as well.
[775.92 --> 777.14] So watch out for that.
[778.28 --> 781.02] Now, I've been in the market to buy guitars in the last couple of weeks.
[781.02 --> 784.30] Joe and I have been talking endlessly about guitars lately.
[785.00 --> 791.46] And a lot of that has involved me F5ing a lot of websites to try and, you know, see what's
[791.46 --> 793.48] coming up on the used market, all that kind of stuff.
[794.08 --> 797.00] And so I thought there's got to be a better way to monitor these web pages.
[797.18 --> 800.88] And I came across an app pick called ChangeDetection.io.
[801.36 --> 806.88] This thing bills itself as the best and simplest self-hosted open source website change detection
[806.88 --> 808.84] monitoring and notification service.
[808.84 --> 809.80] Cool.
[810.56 --> 811.54] This looks really good.
[811.58 --> 816.54] It gives you a little dashboard and shows you when a page was last checked, when it
[816.54 --> 820.94] last changed, and then gives you buttons to check the difference, to recheck it.
[821.76 --> 823.40] This is so neat.
[823.68 --> 824.30] It's really nice.
[824.36 --> 829.54] And some of the examples they ship out of the box are for things like the COVID UK government
[829.54 --> 830.54] page, for example.
[830.64 --> 834.88] So I mean, if you wanted to know when the guidelines change for that, for some reason, you could
[834.88 --> 838.02] have this send you a notification with the diff of what changed.
[838.08 --> 840.64] So you don't even have to go to the website and look it up.
[841.36 --> 845.42] I have mine pointed at the Gibson demo shop, for example.
[845.78 --> 849.90] And, you know, for me, it just lists, it just looks at the guitars that are on there.
[849.92 --> 854.52] And every time a new guitar gets added, I get a push notification through Apprise to my
[854.52 --> 856.22] phone with the link to the website.
[856.22 --> 860.02] So I can just click on the link and go and have a look at that new shiny guitar that I
[860.02 --> 860.48] can't afford.
[862.38 --> 864.50] Linode.com slash SSH.
[864.62 --> 869.28] And Linode has done the work to make sure that Log4Shell is not going to be a problem
[869.28 --> 870.30] on their infrastructure.
[870.42 --> 871.76] It's where we host everything.
[871.86 --> 873.06] They're so dang fast.
[873.42 --> 875.60] And they got 11 data centers around the world.
[875.88 --> 877.98] We got a testimonial from Deckbot recently.
[878.08 --> 880.70] It says, hey, Chris and the Badger, I recently moved homes.
[880.74 --> 884.86] And in the process, I knew I needed to put a home server into storage for about a month.
[884.86 --> 887.40] The server is my Samba server on ZFS.
[887.52 --> 890.56] But I also had two cores and eight gigs of RAM dedicated to a Minecraft VM.
[891.30 --> 894.50] Knowing that they would still want to play while we were moving to the new house, I set
[894.50 --> 899.74] up a $5 nano to install the Minecraft server and upload the world using Linode's game server
[899.74 --> 900.66] how-to as a guide.
[901.30 --> 905.70] Testing it, though, it showed maybe things would work OK, but I saw crashes and we started
[905.70 --> 906.46] to use it more.
[906.56 --> 909.26] And I realized Minecraft was RAM constrained.