m0unds

Member
  • Content Count

    127
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by m0unds

  1. Hi, I installed EAM on a windows 10 machine with a 4k display, and both the product UI and license login are screwy. The product UI can be resized after logging in, but the login screen is cut off and non-resizable (and any error messages are the wrong DPI so are extremely small). Here's an example: *EDIT* product notifications are also borked: as is the uninstall dialog:
  2. have you tried right clicking on the EAM UI application (a2start i think; don't have it installed on this machine) > clicking properties > compatibility tab > high DPI > change to system? the problem with this on a small (sub 22") 4k display is that it makes everything so small it's unusable. not a particularly suitable workaround, i'm sorry to say. overriding the dpi handling for the UI might help, though.
  3. hey, here's the blog post about it: https://blog.emsisoft.com/en/32517/new-in-2018-12-safe-web-browsing-with-emsisoft-browser-security/
  4. considering it was an issue with the mozilla browser addons page that has nothing to do with emsisoft, i think it's completely within the realm of "figuring it out" when resetting the browser to factory remedies the problem preventing him from installing an addon. (i.e. the browser malfunctioned and resetting it fixed it) additionally, firefox sync saves your settings if you allow it to, and it's a zero-knowledge (e2e encrypted) service so there's no reason not to use it unless you hate convenience.
  5. awesome, glad you figured it out!
  6. Oh well - figured maybe something was borked with default browser settings in Windows that may have confused EAM's detection of default browser/active browser What's the URL you're being directed to for installing the Emsisoft browser addon?
  7. Ah, ok. One thing you might try, if you have FF set as your default browser, is to try setting something else (even IE) as default, rebooting, then reverting back to FF post-reboot, and seeing whether EAM detects that you're using it. In Thomas' case, that's addons.firefox.com page not recognizing that he's running FF (which is why I was asking whether he's modifying his user agent or something).
  8. Were they able to reproduce the issue? It worked fine on both of my win10 systems running FF stable (64) Are you using any extensions/addons that change the user agent to spoof another browser?
  9. just in case these weren't known, all of the settings for every product component with a modal dialog (application rules, edit rules, import hosts, add new rule to surf protection, edit extensions for file guard, email notifications, update interval, proxy settings, export settings, set password, connect w enterprise console) are tiny as well.
  10. fwiw, there's discussion about one of the two months that brought the product's average down in this thread:
  11. m0unds

    CLOSED New thing to test

    cool, happy to see this - do you guys have an emsisoft-specific test page we can use to verify functionality? so far haven't seen it block any of the stuff i know EAM blocks (wicar, etc) in firefox on win10 1809.
  12. I have it set to 250% because the windows-recommended 300% makes everything too big.
  13. m0unds

    what is this?

    or an extension that leverages the APIs browsers expose for that specific purpose.
  14. m0unds

    what is this?

    tbh, i think this is more a pitfall of convicting an entire domain/subdomain vs specific path than anything else. i've run into enough weird FPs in shared envs (multiple platforms, AWS/S3/cloudfront, backblaze b2, numerous other providers) that i don't even bother submitting them anymore.
  15. seeing as they track & merge the majority of Mozilla's security code changes in Firefox, I wouldn't count on them continuing to allow code injection if Firefox ends up blocking it in the next few mos.
  16. that's what google would prefer, yes. browser mfgs would prefer third parties stop injecting code into their processes - you already can't do it with edge because of appcontainer isolation, and google and others are tired of being blamed for every browser crash that could be caused by third party code they have no control over. additionally, there are instances where code injection can unintentionally compromise browser security. re: hosts stuff, i would avoid writing large lists to your hosts file as it will significantly slow DNS queries as system has to examine it first. @Ken1943 - as i mentioned, other browsers using chromium (open source project) are merging in the same changes being made to chrome, as is mozilla with firefox (q4 2018 / q1 2019) so this is not purely a "google wants to know everything" concern.
  17. that's fun. firefox doesn't block code injection yet, but it's on their roadmap for q4 2018/q1 2019. i'd also expect opera to start doing it if they merge upstream changes from chromium. *EDIT* Opera is tracking Chromium 69 for Opera 56, and Vivaldi is tracking Chromium 69 for Vivaldi 2.x.
  18. m0unds

    PENDING BB size request

    make that two requests - it'd be a nice QoL improvement, imo
  19. m0unds

    Update Server Problem ?

    Same here, connection error in SW USA
  20. thanks for the reply; glad to hear that, hope we see it soon.
  21. that's great and all, but appcontainer lockdown still breaks EAM's surf protection.
  22. I'm not the OP, but I didn't want to start a new thread, as this one already exists: Is this something you guys are going to be able to work around? Surf Protection still isn't working with Edge on my system (and I can reproduce the issue w/AppContainer lockdown and Chrome as well).