Re:Kristall – a browser without support for CSS/JS/WASM or g...
by shadowgovt on Thursday January 12, 2023 @11:21AM
(#34355885)
HTML and CSS alone allow you to concoct a webpage where a user's input appears to be going to one place but is in fact going somewhere else.
Re:Kristall – a browser without support for CSS/JS/WASM or g...
by ndriscoll on Thursday January 12, 2023 @11:37AM
(#34356228)
The OP link is a browser that doesn't support CSS. Not supporting frames seems like it'd also solve that problem.
Edit: also, in a modern browser, passwords are autofilled by the browser which knows where input is going and can't be tricked. You could make an argument about other sensitive information, but that sounds like it's the same as plain ol' phishing.
Re:Kristall – a browser without support for CSS/JS/WASM or g...
by shadowgovt on Thursday January 12, 2023 @11:40AM
(#34356310)
Agreed.
Unfortunately, there's no language for querying the client "Do you support CSS" / "Do you support frames" without CSS so Google is forced to err on the side of caution and reject browser that don't support JS (because they can query that).
My mental model here is that the browser's password manager autofills a password that the user doesn't even know, and without scripting or dynamic resources, it's not possible to exfiltrate that data automatically. Without styling, form buttons would have a standard look so it's harder to trick the user into submitting something without knowing (c.f. the recently posted fake captcha that tricks users into revealing the visited state of links).