5 ms·
Some more details would be helpful here. Specifically: 1. If PDF files aren't set to open using Firefox's built-in PDF viewer, was the relevant system still vu
by Silhouette 11y ago
Some more details would be helpful here. Specifically:
1. If PDF files aren't set to open using Firefox's built-in PDF viewer, was the relevant system still vulnerable? (That is, if under Options->Applications, PDFs were set to something other than "Preview in Firefox", would this attack still work?)
2. Which were the 8 popular FTP clients potentially affected?
3. Was this specific case all that could be done or was it an example of a wider class of potential exploits? (That is, can we actually trust any sensitive credentials in any applications on any system that has been running Firefox before today? And could we have disclosed other sensitive information that was held in well known local files?)
I do deal with sensitive details, and have access to lots of external systems run by various clients. If there is a real danger here then I need to act. If there isn't, then I would prefer not to spend the next 1-2 days of my time updating everything that could have been silently compromised instead of doing revenue-generating work, and worse, contacting every client I work with to notify them that their security may have been compromised and it's my responsibility.
- jacquesm 11y agoI'm roughly in the same boat as you but what I don't get is if your work is that sensitive then why don't you run with at least ghostery, umatrix and adblock on your machine? The last thing I need is to have to contact a customer to tell them their data might have escaped my desktop computer because I took my browser to some unsafe site. Also: start your browser in a VM.
- Silhouette 11y agoI do run with the browser locked up tight. It runs basically no plug-ins by default, and I have multiple privacy and blocker plug-ins active. I also have a complete log of every piece of software and update to it that has been manually/voluntarily installed in the entire lifetime of every affected system. What I don't know right now is whether any of that actually helps me in this case.
- jacquesm 11y agoI really recommend you use a VM for browsing, or even a physically separate computer from the one that you keep your sensitive stuff on. It's a pain but it's a lot better than any of the alternative scenarios.
- Silhouette 11y agoIn principle I agree, but unfortunately running in a VM is the one otherwise reasonable precaution that I can't realistically take on the machines in question. I do a lot of web development, so if I'm running everything in a VM all the time then I'm not testing using the same browsers that my clients' customers will be. Maybe it would have given some reassurance in this specific case, but in general if those client sites incorporate any third party resources this sort of attack is still a concern.
- facetube 11y agoOut of curiosity, which browsers/versions have you had trouble running in a VM?
- Silhouette 11y agoIt's not so much having trouble as just inconsistency of implementation across platforms. For example, I usually do this kind of work on Windows. I certainly could spin up a quick Ubuntu VM and run Firefox in that, but various aspects of the page rendering might change as a result. Given that far more Firefox-using visitors on most real sites will be running Windows than any other platform, testing with real Firefox on Windows is less error-prone. Ditto for Chrome, etc.
- digital-rubber 11y agounfortunately already too many issues with VM to use that as a safeguard. Better to use a separate computer, hardware.
- JupiterMoon 11y agoGiven that the company that makes the closed source Ghostery add on make their living selling user data I was say that for sensitive work this addon should probably be avoided. Some combination of script and adblocker would probably be a good idea though.
- jacquesm 11y agoIf you're referring to 'Ghostrank' that's opt-in and off by default. If there is something else going on then I'd really like to know about it! Their sources are open and you can inspect them to make sure they don't do anything nefarious so that would have to be quite an elaborate play on their part with the downloads being different than the published source in critical parts.
- JupiterMoon 11y agoIt is closed source. https://en.wikipedia.org/wiki/Ghostery https://en.wikipedia.org/wiki/Ghostery
- jacquesm 11y agoWow, that seriously sucks, they were open source at some point. See: Ghostery was acquired in January 2010 and is no longer open source. This is an old version of the extension. See http://www.ghostery.com/ http://www.ghostery.com/ for a current version. https://github.com/jonpierce/ghostery https://github.com/jonpierce/ghostery They even have a link up to their 'sources' in the FAQ but that leads nowhere.
- snvzz 11y agoRather than ghostery: https://www.eff.org/privacybadger https://www.eff.org/privacybadger
- ZeroGravitas 11y agoNot compatible with Firefox 40?
- mrob 11y ago4. How are "text files" in "text files with “pass” and “access” in the names" identified? "file" command? Extension? 5. Can we get a full list of all the "usual global configuration files" to aid in looking for a pattern in atimes?
- mappu 11y ago> 2. Which were the 8 popular FTP clients potentially affected? Answered elsewhere in the thread (SmartFTP, Notepad++ NppFTP, FileZilla, FTP Explorer, FTPGetter, FTP Now, FTPInfo, Total Commander, Ipswitch WS_FTP, and VanDyke)