Please provide comments and solutions that are helpful to the author of this topic.
- May 31, 2015
- 472
- May 31, 2015
- 472
import the certificate from C:\ProgramData\Kaspersky Lab\AVP19.0.0\Data\Cert.
- May 31, 2015
- 472
Go to preferences & import cert in the following manner... hope it will solve your problem
- Apr 13, 2013
- 3,147
SeaMonkey is the last of the Community coded browser suites. The issue with it is that it is never ever signed (no one wants to put up the cash to get the credentials). Security Apps that look for valid digital signatures will always flag SeaMonkey as untrusted. As long as you do not install Nightlies and just stay with the verified releases you will be fine.
Very smart folk ensure the releases are malware free (we know what we are doing and prefer to keep this browser under the radar). Also no Blackhat in their Right Mind will ever target SeaMonkey as the game would not be worth the candle.
Very smart folk ensure the releases are malware free (we know what we are doing and prefer to keep this browser under the radar). Also no Blackhat in their Right Mind will ever target SeaMonkey as the game would not be worth the candle.
- Apr 28, 2015
- 8,664
Importing manually the KL root certificate, as @yitworths said, should do the trick...
- May 31, 2015
- 472
@harlan4096 hey, when did they change d name of their cert:emoji_expressionless:? It used to be something like '(fake)kaspersky...root certificate' & now it's just '1'. Is their any advantage using a digit?
- Apr 28, 2015
- 8,664
Yes, They changed the cert name with K2019 series
Probably They changed because many users got confusing when They read "fake certificate", so the new name is just 1.cert
Probably They changed because many users got confusing when They read "fake certificate", so the new name is just 1.cert
- Status
Similar threads
-
- Locked
