Credit where Credit is due.
I was critical of Yarbo’s initial response to the security vulnerabilities disclosure. The fact the very first release after the disclosure didn’t mention security in the Release Notes. I thought their response was muted given very very serious issues. I was also critical of their communication processes.
So it has been nearly 12 weeks and Yarbo has been responsive. We have received multiple security updates with the indication all the known vulnerabilities and business processes have been addressed. THANK YOU!
As it relates to communications, I (I suspect like everyone here) received an email announcing the upcoming V3.14.1. Another refreshing and clear indication of positive change by Yarbo resulting from that incident.
Credit is due to Yarbo for being responsive, following through, and making positive changes to their software, development practices, operations, & communications. THANK YOU YARBO
p.s. I still wish Owners could decide when “routine” firmware/software is deployed to their machines. I get pushing the urgent security related fixes asap, but not all releases. I’ve been caught 1,400 miles away from home with 11 days before I returned when my Core received an updated, became unresponsive, and required a simple reboot of the Data Center. I make it a point of not installing updates when I’m traveling. Experienced gained the hard way. 