Jump to content

csg7788

Members
  • Posts

    1
  • Joined

  • Last visited

    Never

Posts posted by csg7788

  1. Hi,

    I don’t consider this issue to be solved.

    I get the same message. 

    I have found the pattern. It appears every time when I visit page  https://www.speedtest.net/ with chrome browser and run a test. I believe it’s related to some add.

    Currently there are options:

    Add to exclusion (which I don’t want to since I don’t trust cs.emxdgt.com),

    Details which opens page https://support.kaspersky.co.uk/common/error/other/13720?cid=KTS_21.3&utm_source=interceptor&utm_medium=product&utm_campaign=KTS_21.3

    and Ignore (Ignore and Remember). According to details page:

    • Ignore the notification. In this case, the Kaspesky application will terminate the secure connection to the website. The website page will open without decrypting the protected traffic and may be displayed incorrectly. 

    I’m not sure if I understand correctly. Does it actually terminate or ignore? I whish there would be an option to Block the page permanently. This should block all the communication with suspicious website.

    Regards Matjaz

     

    Today I started getting the same error as OP immediately after visiting speedtest.net, and continued getting it after closing the tab and later closing/reopening browser. Using google chrome and the free version of Security Cloud 21.3.10.391 (a). See screenshots for Windows version and installed extensions.

    Ignore and remember seems to have stopped it but would appreciate an update on this ASAP beyond “it will be patched in June”

    Are you guys recommending that we add this exclusion cause you don’t think it’s dangerous? Why not tell us that? If not why ARE you comfortable recommending this workaround? Seems sketchy for a security company to give that recommendation without providing any additional information. It would be easy to draw the conclusion that you guys are less concerned with our security and more concerned that we stop pestering you about the issue and just wait for a June patch. 

    Flood seems to be going out his way to be defensive rather than helpful, while at the same time blaming the Kaspersky Community and Technical support processes for the lack of a meaningful response to the issue.

×
×
  • Create New...