This is a minor maintenance release with fixes for CVE-2024-6387, noted as the regreSSHion vulnerability. Additional details and links to the technical discussion and analysis of the vulnerability are available from NAS-129828.
Same here as well, no issues, but then again it was basically one change. To me this is very good as it means this software is extremely stable. A security patch and not a bug fix, love it.
I will admit it caught me off guard. I expected TrueNAS 13.3 when I saw a new announcement. Eh, maybe next time.
Not possible unless iX maintains their own ports tree; and given their aversion to building apps COREs 13.3 version number will be it’s last. #imnotready
Thanks … every test helps. Diverse hardware, diverse configurations, diverse use-cases. We can test all the primary functions in QA, but diversity is important to reliability.
I installed 13.0 on a single disk machine (NOT VM).
Enabled SSH.
SSH’d in and everything seemed good (that was about the extent of my
test because I didn’t have another drive in this machine).
Updated to 13.3 BETA2
Update went well.
I also tested the sidegrade “feature”. The dialog says reverting back to
core is unsupported so I would mention to people this “sidegrade” is a
marketing buzz word and should be approached with caution.
Not sure if this can be “fixed” (aka: forced) on your end but when I
sidegraded DHCP got a fresh IP which made me go plug in a monitor to
see what IP TrueNAS was now on.
This took me about 2 hours to do (from download ISO to now but kids
are involved so I wansnt constantly at the keyboard).
As an experiment I wanted to install FreeBSD and decided to try freebsd-update.
We’d obviously prefer a bug report if you run into any, but short of that the more people running it the better. There’s no expectation of detailed feedback.
Its counter-intuitive, but running the BETA, seeing no issues and providing no feedback is useful. If, however, you see issues, we really need to bug reports.
We look at number of systems that have run the software vs the number of unique bugs reported to assess the quality and decide to move forward.
With 13.0-U6 having a very large number of users, we do not want an upgrade to 13.3 RELEASE to be a poor experience. We need test system diversity to avoid problems.
Out of curiosity, how is this determined? Is it based on the number of downloads or is there some sort of phone home TrueNAS does to tell the mothership what is going on? I suspect the former but I’ve got to ask.
