2 ms·
This headline jumps to premature conclusions; he saw something weird but there's no confirmation yet that it's a Gmail-specific vulnerability. In particular, i
by gojomo 18y ago
This headline jumps to premature conclusions; he saw something weird but there's no confirmation yet that it's a Gmail-specific vulnerability.
In particular, it could be a problem with a misbehaving cache closer to him. (Note especially: in his second screenshot, he's in "Basic HTML" mode. In both screenshots, he's using plain 'http' not 'https' connections.)
It's possible it's Google's fault, but to broadcast that impression without further investigation is unfair to readers -- it's stealing attention with trumped-up claims.