 So, they finally released FreeNAS 11.1-U3, it's available for update and stable. So, this is an important update because of a really big annoyance and I'm really happy they fixed. Now, this didn't seem to affect all the servers, it just affected a few of them, but one of those was mine, so it was an important update to me. And what FreeNAS 11.1.3 also has a very important update for Samba. So, let's run through it real quick here. This is the bug, I'm going to zoom in a little bit here. This is the bug that fixes the FreeNAS-Health warning that goes on via log messages. And if you're like me and you watch your logs looking for potential issues, you don't like a random health warning that's not relevant going in there. And like I said, this didn't affect our win servers, but for those that did, yes, this bug has been quashed. There's a link in here. I'll leave these links in here to the main update so you can read through this yourself. But yeah, this was problematic, we'll just say that, so I'm really happy that that's fixed. Now the other things that are fixed are a couple CVEs in Samba. Now the Samba ones aren't devastating, but they're not good. It's a denial of service attack on the RPC, but the one that's a little bit more worrying, and this is where I like to read the CVE rather than just panic, is this is if you have Samba with a DC configured, domain controller configured with the LDAP server, they found basically a nonprivileged user could change another user's password. It took a certain scenario for this to work. So yes, it's bad, yes, we're happy they fixed it, but not everyone runs this in that same format. But if you do, definitely patch it, because this solves that problem. And of course, Samba should never be public facing, I'm going to throw that out there. It shouldn't be facing internet, but we know from Shodanskans it is. So it should be an internal thing, but either way, once someone's in your network, that doesn't mean you should let down your guard and not have all these things patched, but the details are in there. The last bug is address arty and use. I hadn't seen this one. Prevent address arty and use by not using SO reuse address. I hadn't seen this bug before, so I don't know why it takes you to the login page for that. But the update on FreeNAS, if you're not sure how to do it, pretty straightforward, you're going to go over here to system, then you're going to go to update and you can, as long as you're on the stable branch, unless you're feeling frisky and want to go to the nightlies, you can go ahead and jump on that. So that's where you go for the FreeNAS update. Pretty simple to update. It does take a little while. Side note, in case you didn't know, this is the history of updates. Do check before you do the update on this right here. Make sure you have enough room because you can have some problems there. And I'll give you an example because I think this has come up with some confusion. This is on reboot now. And you can say activate this if I want to roll back to the U2 version in case there's a problem. But I know the system works. I know there's not a problem. And you may have more in your history. Maybe you want to keep one or two versions. I generally just keep one previous version, but this is my demo machine. So I'll show you how you delete a version. So this is the active one. Don't mess with this. And we're going to go ahead and hit delete. And now we're only down to one. Now, if you've never deleted anything, you have the initial install and all of them down there. But you just want to make sure that you have, for whatever you're using for your storage, a lot of people using a thumb drive, which is fine. Make sure you don't run out of room on it. And this is the easy way to do that. So you can just go ahead and do a status of it or check it out and make sure it's working. But just before you do an update, make sure you have enough space for the update. Little side note there, but that's it. It's pretty straightforward. The update worked. I didn't have any problems. Please be patient when it updates. It does take a little while because it has to download. It has to install it. And then if you watch the terminal while it's installing, you'll watch it go through and replace all the files and do all the stuff that it does. It takes a little while. The patient depends on the speed of your computer, but even on this computer, which is a Xeon X570 at 3 GHz with lots of cores, it still took about 10, 15 minutes to get the update done. So your mileage may vary. If you have an older slower system, be real patient with it. The U2 update took a little while as well. So just want to throw it out there. It is available. It does fix that samba vulnerability, so get patching on there. And so far, so good. I've patched a couple of machines that we have and haven't any issues. I'll keep you posted or I'll file a bug report if there's a problem. All right. Thanks for watching. If you liked the content here, like and subscribe.