 Time here from Orange Systems and TrueNAS 12.0 update 4 was released on June 1st 2021 And yes right away is day of release I went ahead and updated well all of my true NAS servers because I wanted people to answer questions if the upgrade worked if the upgrade Broke things and well it did break something and don't worry the team over at TrueNAS is on it the CPU widget broke That's annoying not that annoying. No, because honestly, I don't stare at the CPU widget much That's where right here. We have little bars that are normally there. They're missing it still tells us percentage But don't worry a ticket's been opened and they're on it. So that'll be probably fixed. I'm guessing an update five It doesn't have a target for release yet, but the engineers are aware That's the only problems I have to report and I want to get that out of the way before we dive into what's new And what changed in the system, which this is a minor update This is not like a major release version So that means it's just a lot of bug fixing and quality control issues and the issues that you report and people open tickets for Are the ones that get priority and get fixed But before we dive into this video if you like to learn more about me or my company head over to Lawrence systems that conflict a Hire sure project. There's a higher spot and right at the top if you like to support this channel in other ways There are affiliate links down below to get deals and discounts on products and services We talk about it on this channel and the consulting does of course include true NAS server consulting I should do a lot of that. Well, let's talk about this. Well bug minor issue. I uploaded it So awesome that is great that that's going on from a looks standpoint This is one system here at true NAS 12.0 u4 that I have pulled up and You're not gonna see any major difference because they didn't redo the UI or anything like that Like I said, it's a minor update. Let's talk about the minor update and what got done Now one thing I'll actually jump to the bottom because a lot of people seem excited about this me less So and I just bring it up because I've not been the biggest fan of two and a half gig I don't see that mass adoption of it ten gig is pretty Reasonable now it's been out for a while and I think the two and a half gig standards are just so people can reuse a lot Of existing wiring so I guess there's a market niche for it We just aren't seeing as many people ask about it because they look at the price difference between two and a half And ten gig and seeing it as very small, but of course if you're running older cat 5e Yes, you can run two and a half gig on that So If there are certain edge cases use cases for it if the servers are not local to each other where you would just run a You know low-cost ten gig cable, so I get it But I know that's something a lot of people will be excited about even if I'm not next thing and since we started the bottom Let's go up minor web UI reporting issues including display of more jails per page Yeah, just a space efficiency usage So when you have a lot of jails, which I don't use a lot of jail So I couldn't really make a different between point a and point B I was gonna screenshot and realize I'd have to set up a bunch of jails that I'm not using so but yeah It's more efficient use of screen space now. I have done a video on I believe it's pronounced min. I owe This is the s3 system That you can both well You can load either as a plug-in or as a feature that's natively built in and this allows you to use your true Nassas a s3 storage target and s3 compatible So it's not actually Amazon s3 But this is actually cool for a lot of applications or people who run their true Nass maybe in a colo server and want to run their own application instead of tying it to something like Amazon But it's you know a lot of applications have dependencies on s3 This is what that's for and the updated to support for api b3 security updates Is important we're gonna jump to that after we talk about replicate web UI improvements. I actually Have done videos on this I'm gonna have to go through and I haven't really they look the same, but I guess there's a few minor changes on there I did a video talking about this and maybe from that there's probably a few minor changes So I have opportunity for me to update the video and let's dive deeper into the security updates I really like the way they did this they did the security report for churness 12.0 u4 I'll leave a link to this so you can read through the details but these are one of those little nuances that matter a lot and It's when you find a CVE in one of the components that is inside of an open source project specifically We're talking about churness here, of course, but this applies to other platforms as well Sometimes when it's getting integrated. They don't use or don't have the CV exposed So while it should be fixed and it should be patched It's one of those how critical is it in terms of what is the actual threat this represents an example Here is the free type one where churness does not allow to upload PNGs to trigger this attack So they did update it and they did fix some of the issues in The open VPN and things like that that's down in the bug reports But these are still some of the known issues for 12.0 u4 and it's one of those things where you'll find people going well, I can't use it It's insecure to get a broken version of free type in there currently and it won't be out till the next update But the other side of that is they've done it in a way that it's not Exploitable and I just wanted to bring it up because I thought it was interesting And I thought this was wonderful that they put this out there so you can kind of go through and say all right what about this issue or this issue because using this version and You know not allowing a user to use XML to trigger the attack with the Libre Ex Lib XML to library. I mean that was a little detail same with this our sink 3.1 3 underscore 2 is vulnerable. Well, no, they didn't compile it with the same Zlib so it's not and but I love that they listed all this so you can kind of go through and these are some of those scan results And they have answers to each one of them So for those of you that do have to go through and you know are Especially when you're using this enterprise environment looking at these little issues and the versions of each component That's within one of these projects It's great when you see a company documenting that they implemented in a way that is not vulnerable now back over to here that is 18 improvements and 81 bug fixes there's obviously a lot of little details that I always leave here You know this may or may not affect you but there's just a ton of little things that had to be fixed and of course they have in here and It's something a couple people mess with me about and I kind of get what they're what they did here Python upgrade to several permits to reduce memory leaks and probability of crashes of core middleware process this issue Happens rarely does not impact ongoing data services and have proven to be difficult to reproduce This is basically the Python control system in between the middleware as they refer to that apparently hit some crashes in it And I had someone message me about it I said I I don't I mean I'm more than happy to help of course if I can reproduce the issue But ultimately I'm not the developer you need to be able to reproduce the issue Document it in their ticketing system, you know maybe starting a forums or the discussion over on the true NAS forums and you know These are those edge cases that come up and this comes up even with certain cards that I know they have fixes for down in a bug fix Like if you have this particular card, they found this particular error under these particular circumstances That always comes from community You know documenting making a reproducible. This is the steps I need to reproduce this so the developers can also reproduce those steps and Trigger the condition and then look at the errors and then fix the condition Also in here is just some general open ZFS speed improvements for both high-performance systems small and high-performance systems performance during scrubs while under high CPU load should be more reliable and This is one of those things again edge cases when you have a lot of things going on in a scrub Apparently there was a time when the CPU would become essentially Overstressed and caused the whole system to lock up so they've done more improvements on there So all these little small incremental improvements So if you're still hanging out on 11 waiting for one of those 81 bug fixes that are listed in there to be complete Maybe this is the time you move off of 11 and finally get on 12, but either way it's a welcome update I've updated the system nothing bad happened nothing major happened all the functions that we have here in the business because these are production systems for us are working fine And we'll slowly start rolling this out on schedules when we have you know the time to reboot them that our clients and get Everything back up to date. All right leave links all this down below and thanks And thank you for making it to the end of this video if you enjoyed this content Please give it a thumbs up if you like to see more content from this channel hit the subscribe button and the bell icon To hire a share project head over to Lawrence systems calm and click on the highest button right at the top to help This channel out in other ways There's a join button here for YouTube and a patreon page where your support is greatly appreciated For deals discounts and offers check out our affiliate links in the descriptions of all of our videos including a link to our shirt store We have a wide variety of shirts and new designs come out. Well, randomly, so check back frequently And finally our forums forums that Lawrence systems commas where you can have a more in-depth discussion about this video and other tech Topics covered on this channel Thank you again, and we look forward to hearing from you in the meantime check out some of our other videos