Hello Jernej, Monday, June 20, 2011, 5:25:56 AM, you wrote:
> It does explain why the problem was solved/worked around: Kaspersky is > doing a man-in-the-middle attack on your SSL connection to be able to > inspect messages. To make this work, it adds it's own root certificate > to the Windows certificate store, so when programs check if the > certificate is trusted, they find it is - but this only works when the > programs use Windows' own certificate store. By default, The Bat > doesn't, so it alerts you that something weird is going on. I had a feeling that Kaspersky was the cause. I had thought about going to the Kaspersky web site and seeing if I could pick up their cert and installing into the Bat cert folder. Would that work? -- Best regards, Dean ________________________________________________ Current version is 4.2.42 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
