Keumars Afifi-Sabet/IT Pro
Google has mounted a major bug in a Chrome OS steady channel update unveiled earlier this week that locked Chromebook buyers out of their machines.
The verification mistake, current in edition 91.1.4472.165, arrived as a final result of a single character typo in a string of code in Chrome OS’s Cryptohome VaultKeyset, which is the part of the working system that holds user encryption keys.
The string in issue was a conditional statement that involved a solitary ampersand, ‘&’, as an alternative of two ampersands, ‘&&’, which is the AND operator in C++. As a final result, the conditional assertion was broken and intended that Chrome OS was not able to test consumer passwords towards those stored.
This intended, in follow, that all end users who experienced updated to 91.1.4472.165 had been achieved with error messages, even if they experienced entered the proper password to obtain their person account. For some customers, their devices have been even stuck in a boot loop that intended they could not even arrive at the login monitor.
Google rolled out the buggy update through its secure channel final weekend, which bypassed several of its screening channels which includes the ‘canary’, ‘dev’, and ‘beta’ channels.
It was then nearly right away fulfilled with common grievances on social media platforms this sort of as Reddit. There had been numerous threads and hundreds of posts on the r/chromeos web page from consumers reporting they had been unable to entry their devices correctly, together with messages warning others not to update to the most current edition of Chrome OS.
Google’s engineering team immediately determined the bug and halted the rollout of the Chrome OS update on Tuesday, promising a new model the pursuing working day. In the meantime, the workforce encouraged possibly manufacturing facility resetting the system or rolling again the Chrome OS system to a prior edition through USB. The organization produced model 91.1.4472.167 the subsequent working day.
This is the 2nd main bug which is slipped into the secure channel for Chrome OS updates this thirty day period. One more bug that slipped into a ultimate launch induced exceptionally substantial CPU utilization spikes, in accordance to Android Law enforcement.
Some sections of this post are sourced from: