Hello Jernej, On Tue, 22 Mar 2016 12:00:44 +0100 GMT (22-Mar-16, 18:00 +0700 GMT), Jernej Simončič wrote:
> On Tuesday, March 22, 2016, 5:39:32, Thomas Fernandez wrote: >> 22-Mar-16, 11:26:51: FETCH - Issuer: generated by avast! antivirus for >> SSL/TLS scanning, avast! Web/Mail Shield, avast! Web/Mail Shield Root. > Your antivirus is doing a MITM attack on the connection, which is why > it's failing. Thanks, that was it! I had already download that TB! version again and reinstalled, hoping that the certificates will show up in the ABD, but they didn't. Checking here on my home PC, I don't see any certs in the RootCa addressbook either... I disabled avast! in the office, and could use the computer without problems. Windows 10 automtically enables Windows Defender when no other antivirus is enabled, so I was reasonably safe (I hope). I only wonder why there was no MITM problem with avast! under Windows 8, and it suddenly appeared after the Windows upgrade. > It might work if you switch TB to use the Windows certificate store, > but such MITM actually leaves you more vulnerable. How would I do that? - I do like avast!, and I don't know whether Windows Defender is as good. -- Cheers, Thomas. http://thomas.fernandez.hat-gar-keine-homepage.de/ Message reply created with The Bat! 7.1.18.2 (BETA) under Windows 7 6.1 Build 7601 Service Pack 1 ________________________________________________ Current version is 7.1 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
