Earlier quoted context omitted.
As long as the extension UI is rendered where the page can also render something, it will be vulnerable to phishing. E.g. https://www.seancassidy.me/lostpass.html
Correct, that’s why it’d be preferable to have it handled in the browser itself. If it’s a message in the browser chrome itself, and not as in the page, it is possible to add distinguishing UI. With the current system, it’s literally impossible to distinguish the UI
Grammarly shared its tokens with all websites
111–120 of 176 posts
Re: Grammarly shared its tokens with all websites
#112How did they fix it?
Re: Grammarly shared its tokens with all websites
#113Earlier quoted context omitted.
As an open-source extension developer, I wish there was a way to prove that the extension uploaded is generated from a specific git commit. It wouldn't solve everything, but it would make it easier for anyone to audit the code and know that it actually matches the code I've uploaded.
Indeed. I was thinking about this, and would argue this should really not only exist... but be the only way extensions with this level of wide-sweeping access should be permitted to be published. Chrome team, if they were security-focused, would not permit any closed source extensions which have access to all website data. People don't seem to understand sometimes that if an extension has this sort of access, you nee…
Re: Grammarly shared its tokens with all websites
#114Another nice thing about Grammarly is that the plugin just blindly detect contentEditable inputs and start screwing with their content. This very much breaks modern WYSIWYG web editors, which typically expect to have control over the editable content. Which more or less comes down to "move over page scripts, I'm a browser plugin, this is _my_ webpage now".
For better or for worse, between browser extensions loaded by the end user, and "tags" injected by your well-meaning business analytics team - see my comment here: https://news.ycombinator.com/item?id=16314501 ), the extension ecosystem has become the new Internet Explorer in terms of compatibility testing. Luckily most of the workarounds are trivial, but it's essential to have good QA on actual client machines if you're doing, well, anything at all.
Re: Grammarly shared its tokens with all websites
#115I feel like the first thing we should talk about is how this is effectively a keylogger, similar to Windows 10's inking and typing setting, albeit with likely poorer security. Collecting everything you type into a web browser (or MS Office) and sending it to them seems like a really bad idea.
Why is this story not bigger news? Grammarly is excreting ads into my eyes before nearly every YouTube video I watch, yet I don't see any mainstream sites covering this.
Re: Grammarly shared its tokens with all websites
#116Earlier quoted context omitted.
Not sure if you're using the credential "autofill" feature, but somewhat recently there was an attack in which their autofill extension could be tricked into "autofilling" specific sites' credentials on a malicious webpage. (Not sure if this has been fixed by LastPass) The fix for that was to not use autofill and revert to manually grabbing your username/password when filling out a login form. Aside from that, I am n…
LastPass has been very diligent in fixing issues like the one you list. Usually very quickly (sometimes in hours, not even days.) And most of the issues you've read about with LastPass have been fixed before being disclosed because of how responsive they are. Users still need to practice skepticism and ultimately it is their responsibility to protect their passwords. But LastPass has been a very good citizen when it…
Re: Grammarly shared its tokens with all websites
#117I feel like the first thing we should talk about is how this is effectively a keylogger, similar to Windows 10's inking and typing setting, albeit with likely poorer security. Collecting everything you type into a web browser (or MS Office) and sending it to them seems like a really bad idea.
Isn't this also true of nearly all installable keyboards on mobile devices?
Re: Grammarly shared its tokens with all websites
#118Re: Grammarly shared its tokens with all websites
#119Earlier quoted context omitted.
Correct, that’s why it’d be preferable to have it handled in the browser itself. If it’s a message in the browser chrome itself, and not as in the page, it is possible to add distinguishing UI. With the current system, it’s literally impossible to distinguish the UI
Chrome has extension popups that kind of do this - they are pointed to the icon in the extension bar. Does Firefox have anything like that?
Re: Grammarly shared its tokens with all websites
#120Earlier quoted context omitted.
> I personally stay far away from password managers I am curious how you manage your passwords.
Use an out of band password manager, whose key is never transmitted over a network. Or a notebook that is physically secured. There are a number of solutions for password vaults, and you can use a variety of means to synchronize them if needed. The notion that it's a good idea to trust a browser extension for secrets management is pretty bizarre to me if you're protecting high value assets.