3 ms·
A core problem with the proposal is that it did nothing to address web extensions. So sure you know someone is using the real Chrome, but they could be using a
by charcircuit 3y ago
A core problem with the proposal is that it did nothing to address web extensions. So sure you know someone is using the real Chrome, but they could be using a web extention that scrapes stuff or acts like a bot. There needs to be a way for sites to verify they are on a real Chorome that is operating to specification, but also that no web extentions are able to interact with the page itself.
- amarshall 3y agoWhy does there “need” to be a way to do that? What benefit does it give the user?
- charcircuit 3y agoPlatforms they use having less spam. Their data not being in big datasets of scraped user information. Their accounts not being compromised from credential stuffing attacks. Not having to deal with cheaters in multiplayer games or games with high scores.
- shadowgovt 3y agoIn the context of the original goals of WEI being good goals. I believe GP's point is that with Chrome extensions being unaccessible from the attestation standard, WEI wouldn't accomplish its goal.
- hooverd 3y agoMuch like the Patriot act it was for your safety and security.
- hooverd 3y agoSo the problem was that it didn't steal enough control away from users?
- charcircuit 3y agoNo, the problem was the attestation was not of the entire stack. By not attesting the web extentions someone could create malicous web extentions to bypass the security of the system. As a reminder attestation does not steal control away from users. They are free to use whatever software and do whatever they want. They just will not be able to attest to a server that they were using a trusted stack in the case they were not.
- hooverd 3y agoSure, if you have a fundamentally different view of the Internet as approved dumb terminals rather than devices communicating over protocols. Say it with with your chest. Saying you'll still be allowed to run your own programs here is like saying you'll still have free speech as long as you stick on the approved free speech zones.
- charcircuit 3y agoOn the internet users have never had total control over the websites they have interacted with. The owner of the website has the control. Attestation doesn't change this. Users control their machines and software and websites control theirs.
- hooverd 3y agoAttention means that websites de facto control user's machines. If everyone uses it and they will you don't have a choice.
- charcircuit 3y agoNo, it doesn't. Gambling sites don't control people into becoming 18+. Being of the appropriate age is just proof the user gives before the websites offers service. Similarly by having people prove what software stack they are using to a website, that website may be able to improve the user experience for everyone.
- jauntywundrkind 3y agoWay to be the dude to show up and argue, is it cruel and evil enough ? You sir are in flagrant violating of rfc8890 & need to get your head screwed on straight. The browser is called a user-agent because it is grants the user agency. It does not represent the sites; it is the user. It should empower not restrict them. https://datatracker.ietf.org/doc/rfc8890/ https://datatracker.ietf.org/doc/rfc8890/
- charcircuit 3y agoRFC8890 is about IETF specifications. WEI was not an IETF specification. The relevant standards body would have been the W3C. I am not currently in the process of submitting a standard to the IETF. The IETF is not relevant here. Regardless, attestation benefits the user as it allows the websites they use and share data with to be more secure. WEI didn't make sense because it didn't actually prove the integrity of anything.
- jauntywundrkind 3y agoIP, TCP, and QUIC are all IETF standards & in use here. The base of the pyramid, governing the internet as a whole, says the Internet is for end users. That doesn't seem in the slightest bit hard to see. It's unclear that websites would be more secure by virtue of having a Google or Microsoft or Apple attested OS. What examples have we seen of users running their own OS contributing to a web host's security issues? Got anything? Probably not! WEI has always been of dubious use. Your original claim that extensions needed to be blocked was an explicit anti-goal of web. Users obviously have a right to extensions, which allows for accessibility affordances, for example. Would you also propose turning off view source and the debugged? What other nastygram blocks of shit do you propose smacking users in the face with? It feels like you are trying really hard to be obtuse negative & nasty to users, and throwing absurd ridiculous arguments out to anger people, who care about users.
- charcircuit 3y ago>IP, TCP, and QUIC are all IETF standards & in use here. The RFC is about the development of those standards. It is not talking about the usage of them. >What examples have we seen of users running their own OS contributing to a web host's security issues? For example there are scripts that take lists of email password combos and send network requests to attempt logging into these accounts. Then using these accounts the attackers do malicious actions. Platforms that make it harder or more expensive to automate things will have less people using them abuse services. >Your original claim that extensions needed to be blocked was an explicit anti-goal of web. If sites only want to allow input injection that comes from preapproved password manager extentions they should be able to get proof of if that's the case. The alternative to the browser blocking the extention is that the site could ask the user to disable the extention or just provide an error that the input came from an untrusted source. There are some different options in how this could be handled. >Users obviously have a right to extensions, which allows for accessibility affordances Yes, but my concern is mainly with the proof part on the server side. So the server can be sure that actions taken were not being done by an untrusted extention. Accessiblity also needs to be carefully considered as bad actors may use accessibility features to bypass security. >Would you also propose turning off view source and the debugged? No, I have not seen a big demand for keeping code a secret. For the relevant problems trying to hide the come is security by obscurity. >What other nastygram blocks of shit do you propose smacking users in the face with? I don't indented to smack any users. 99% of users will not even notice anything has changed, but attackers will realize that their job just got a lot harder. >It feels like you are trying really hard to be obtuse negative & nasty to users I feel if you had to deal with protecting a website from bad actors you would appreciate my viewpoint.