uit 0 Posted June 11, 2020 Share Posted June 11, 2020 6/10/20 7pm PST Within the past 12 hours or so, SSL/TLS protocol filtering, Interactive mode has stopped functioning in ESET IS 13.1.21.0 on Windows 10 1909 with Google Chrome 83.0.4103.97 (64-bit). Usually, when in Interactive mode, ESET IS detects SSL Certs and prompts whether Certs should be ignored or scanned. ESET IS is no longer prompting. It completely misses the Certificate and no prompt appears. Automatic mode still seems to work normally. This same problem also occurs on a fresh Windows 10 install with ESET IS 13.1.21.0. Can this be fixed, please? Link to comment Share on other sites More sharing options...
ESET Staff Posolsvetla 15 Posted June 12, 2020 ESET Staff Share Posted June 12, 2020 I was able to reproduce this issue with Internet protection module 1398. Do you have the same version? Link to comment Share on other sites More sharing options...
itman 1,538 Posted June 12, 2020 Share Posted June 12, 2020 (edited) If your objective by switching to SSL/TLS protocol scanning Interactive mode is to exclude Eset's scanning of a given web site, this can be done manually. Refer to the below screen shot. Open your browser. Then open Eset GUI. Then select Setup -> Internet protection -> Web access protection -> Web and Email -> SSL/TLS -> List of known certificates -> mouse click on the Add tab. Enter URL for the web site whose certificate you wish to exclude from scanning. Mouse click on the OK tab. Eset will auto populate the certificate data. Finally, set Scan action to Ignore. Click on OK tab and every subsequent OK tab to save your changes. Edited June 12, 2020 by itman Link to comment Share on other sites More sharing options...
uit 0 Posted June 13, 2020 Author Share Posted June 13, 2020 On 6/12/2020 at 6:31 AM, Posolsvetla said: I was able to reproduce this issue with Internet protection module 1398. Do you have the same version? Internet protection module: 1388.4 (20200611) Link to comment Share on other sites More sharing options...
ESET Staff Posolsvetla 15 Posted June 16, 2020 ESET Staff Share Posted June 16, 2020 I wasn't able to reproduce it with the version 1388.4 The version 1398 was released only for a few days and than replaced with 1388.4 The issue is only present in the version 1398 and will be fixed in 1399 Link to comment Share on other sites More sharing options...
Recommended Posts