text stringlengths 9 408 |
|---|
• Discussion of a hypothetical show idea similar to "Wife Swap" but with systems and infrastructure |
• Overview of the host's current server setup, including its age and previous operating systems |
• Mention of Cloud Guru as the sponsor and invitation to engage on social media |
• Host's personal Twitter account and contact information for the show |
• Discussion of self-hosting and infrastructure choices, including Proxmox and Arch Linux |
[0.00 --> 3.32] Coming up on today's show, we discuss the Home Assistant Security Bulletin. |
[3.76 --> 9.58] I've got some pretty cool Bluetooth low-energy OLED temperature sensors for you from Xiaomi, |
[10.00 --> 12.62] and we get philosophical in the feedback section. I'm Alex. |
[12.98 --> 15.74] I'm Chris, and this is Self-Hosted 37. |
[16.92 --> 20.74] You know, it was only the last few weeks I realized that we just sort of blew right past |
[20.74 --> 22.38] our one-year anniversary in September. |
[22.92 --> 23.74] We're one. |
[23.98 --> 28.74] Yeah, and I think it was just because we were doing the whole going independent thing again. |
[28.74 --> 30.66] And so we just had a lot on our plate. |
[30.96 --> 32.66] What's your opinion on first birthdays? |
[32.96 --> 36.26] I think the show's been really well-received, and it seems like it's still growing, |
[36.42 --> 38.04] but it's found its audience. |
[38.52 --> 41.80] And I think it's a good first year, especially because we're not weekly. |
[42.10 --> 45.36] And so for some podcasts, that can be rough, but it doesn't really seem to have held us back. |
[45.72 --> 49.26] I wasn't talking about that. I was talking about kids, first birthday. |
[49.50 --> 52.76] Do you make a whole big deal about it? Because obviously, they're not going to remember it. |
[53.00 --> 54.20] That's true. That's true. |
[54.20 --> 58.84] Yeah, I don't know. I feel like for podcasts, it's a good sign that it's a stable podcast, |
[59.20 --> 66.20] but there's like kind of this, the real, I think, real landmark for a podcast is five years. |
[66.32 --> 67.94] That feels like the one you celebrate to me. |
[68.40 --> 71.76] Yeah, you've done a few that have reached episode 300. I think for me, that's a big number. |
[72.14 --> 77.04] Yeah, that's also a pretty big one. Yeah, so congratulations, though, on the anniversary. |
[77.16 --> 80.92] We thought this seems like the perfect episode to follow up on a lot of things because of that. |
[80.92 --> 87.34] You know, it's going to take us 11 and a half years, twice a month, to reach episode 300. |
[89.02 --> 93.02] Maybe we'll have to step it up at some point. Maybe we'll go daily for a last little bit. |
[93.74 --> 98.94] We have flirted with the idea of weekly, but you know, with going indie, you've had so much on your plate again. |
[99.70 --> 102.50] It's not really been feasible for both of our schedules yet. |
[102.86 --> 107.64] Yeah, life is busy, but you never know. Things change in the future, but right now we don't have many plans to change it. |
[107.64 --> 113.00] We have discussed it from time to time. The future is, well, it hasn't happened yet. |
[113.62 --> 120.32] But this episode has happened. It's happening right now, and it's brought to you by a Cloud Guru, the leader in learning for Cloud Linux and other modern tech skills. |
[120.70 --> 126.82] Hundreds of courses, thousands of hands-on labs. Get certified, get hired, get learning at cloudguru.com. |
[126.82 --> 134.98] I got a rather alarming set of emails and Reddit posts from the Home Assistant project this week about a security bulletin. |
[135.72 --> 143.62] And I wanted to get your take on how they're handling it, because to me it seems like controlled, well, not even controlled. It just seems like chaos over there. |
[143.98 --> 149.06] Yeah, they're really trying to get the word out. That's one of the reasons, I think by now, when this episode comes out, people will know about it. |
[149.06 --> 154.56] But just because this seems to be really important, I even got a notification again this morning via their Discord community. |
[155.08 --> 158.18] So there was a security bulletin put out by the Home Assistant project. |
[158.18 --> 171.20] We will have the blog post linked in our show notes, but there's not much to it, other than it just strongly encourages you to update as fast as possible and spread the word as far as possible. |
[171.50 --> 180.00] There is a specific callout in the blog post to an issue with custom components, which are not reviewed by the core Home Assistant team. |
[180.00 --> 184.04] But otherwise, there's really zero information in the bulletin as we record. |
[184.16 --> 186.16] This is several days after the bulletin as well. |
[186.70 --> 192.84] We were told there would be an update with more information, but it so far hasn't shown up anywhere. |
[193.78 --> 204.98] However, we do have several questions that we'd like to have answered, like which integrations were leaking stuff, under which circumstances were those integrations leaking stuff, and does the update that's been released fully address those issues? |
[204.98 --> 210.32] Or, as some are speculating right now, is it just merely mitigating them? |
[210.80 --> 215.30] Will there still be some risk after updating if we use whatever integration this supposedly was? |
[215.34 --> 220.42] So there's definitely questions that haven't been properly answered by the Home Assistant project right now. |
[220.96 --> 223.18] I wonder if that's because they just don't have the answers yet. |
[223.56 --> 224.64] You speculate, really. |
[225.30 --> 229.70] And at this point, I want to just let the audience know we are recording this a couple of weeks ahead of time. |
[229.92 --> 232.56] I've got some personal stuff coming up, so it's unavoidable. |
[232.56 --> 240.04] But, you know, from my perspective, I want to see like CVE-style clarity here. |
[240.20 --> 241.38] I want to know what the problem is. |
[241.46 --> 244.50] I want to know what they've done to fix it or that they haven't fixed it. |
[244.66 --> 253.62] I actually don't necessarily mind if they haven't because at least I know what the problem is, so I could maybe go and try and contribute to creating a fix, perhaps. |
[254.06 --> 255.02] Yeah, I'm sure they're very busy. |
[255.44 --> 260.64] But there are basic questions like if I didn't use any custom components, do I have any cause for concern? |
[260.64 --> 269.34] Now, if you go by the code, because it's an open source project, it looks like maybe they caught that some nasty things were happening via the HTTP API. |
[269.34 --> 274.52] Seems like maybe they've added some basic filters to the code for some common web-based attacks. |
[275.12 --> 276.66] But really, the context matters here. |
[276.74 --> 278.32] So that's only something the project can provide. |
[278.84 --> 290.94] Yeah, I see some stuff in the code for one of the commits that's referenced in the forum post about the security bulletin about file injection attacks at certain web URLs as well as SQL injection protections and stuff like that. |
[290.94 --> 292.92] So who knows what's going on? |
[293.48 --> 302.42] This is where it's a really tricky balance, especially for an overburdened project and especially a new one that hasn't really had to deal with a security issue quite like this yet. |
[302.92 --> 309.06] There is a real high standard for a platform, a really high standard of clear communication. |
[309.06 --> 314.88] And even if that communication is a status update that they don't have the full report yet, it needs to be communicated. |
[315.38 --> 316.84] It's a hard lesson to learn. |
[317.00 --> 318.76] You also have to create process. |
[319.12 --> 321.92] It's a human problem as well as a process problem. |
[322.44 --> 326.56] But clear communication is critical for any kind of popular platform. |
[327.42 --> 330.94] And I know that they're very busy, but that's always going to be the case. |
[330.94 --> 336.96] And as more and more people integrate their homes and businesses around this, it's pretty important that we know what's going on. |
[337.60 --> 342.80] That's where the communication is probably going to be a bit of a learning opportunity in the future. |
[342.98 --> 350.72] But it also reminds me that they're still, you know, as far as a project goes of this scope, relatively young. |
[351.34 --> 354.12] And they still have things that they're going to have to figure out. |
[354.12 --> 364.80] And it's not why it's a knock when I say this, but it sort of speaks to why I'm not a huge fan of their entire integrated approach with the OS and Home Assistant and the supervisor. |
[365.44 --> 370.50] I'm not a huge fan of this project building an OS. |
[372.04 --> 381.38] With these types of security things, with the underlying platform, that's just an area I'd like to outsource that work to the folks at Canonical, Red Hat, or Debian. |
[381.38 --> 385.12] I just don't really prefer having the project control the entire stack. |
[385.46 --> 389.12] I understand why they do it, and it's an entirely separate conversation. |
[389.30 --> 397.68] But it's one of my arguments why I hope they keep making it possible for folks like me to deploy the entire Home Assistant experience on the OS of my choice. |
[398.02 --> 406.86] Because just for my personal comfort and just the way I view the world, I like to know that a vendor like Red Hat or Canonical is behind the server OS that I'm using. |
[406.86 --> 416.36] I mean, I see on a daily basis at work, a lot of the stuff that goes on behind the curtain of maintaining a kernel, of maintaining a Kubernetes distribution and that kind of stuff. |
[416.48 --> 418.68] And it's an astronomical amount of work. |
[419.00 --> 420.14] And I've got to agree with you. |
[420.14 --> 440.46] I think if the project were to take the limited resources that they have and kind of share them out in their area, well, not share them out, but like delegate the responsibilities of the more complex tasks like building an OS to vendors whose day job it is and who have 25 plus years. |
[440.58 --> 443.70] I'm looking at Debian experience in doing this kind of stuff. |
[443.70 --> 449.16] And then they can focus on what they're good at, which is building a brilliant home automation platform. |
[449.58 --> 450.84] But to their credit, they caught this. |
[450.98 --> 456.66] And the other thing I think they've done right in this process is they have communicated the need to upgrade. |
[456.88 --> 464.52] They haven't been particularly great about communicating why other than security, but they have been very good at getting the word out. |
[465.20 --> 469.34] And there is a pretty safe process to do that upgrade. |
[469.34 --> 473.86] So I decided to do it over the weekend so that way I could report back here on the show. |
[474.48 --> 480.44] And my setup is it's Ubuntu 2004 running on a Raspberry Pi 4. |
[480.78 --> 487.56] I can't even remember how I set it up now, but I have the full supervised home assistant setup so I can install the add-ons and take snapshots. |
[487.98 --> 491.88] And I really love that setup, even though it's not technically a supported setup anymore. |
[492.18 --> 495.72] But I went into my home assistant supervisor and I clicked update. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.