Hm. Chrome released a patch for a CVE, version 98.0.4758.102
But Context Aware Access only accepts MAJOR.MINOR.PATCH ie: 98.0.4758
Why does Chrome versioning work like this? Why is that security patch not part of a normal patch version?
Conversation
Replying to
chromium.org/developers/ver
It's MAJOR.MINOR.BUILD.PATCH where BUILD.PATCH uniquely identifies the release by itself. I don't think they ever use MINOR in practice due to having such a quick release cycle for major releases (4 weeks).
In practice, BUILD is the same for an entire major release since it represents it being branched off the development branch. The reason for this system is so that you can trace back the major releases to where they were branched off the development branch. It's all a bit silly.
1
Replying to
It's super annoying bc I wanted to force .102 since that patches a vuln with an ITW exploit :(
I guess its a gsuite issue though ultimately. Sigh, will report.