On 01/08/14 12:19, HenriK wrote:
<Snip>
Eventually, I posed my problem to the Kaspersky tech support people.
Again, I was using Kaspersky Internet Security (KIS) 2014. I did not
experience the problem with KIS 2013. It never occurred to me that KIS
could be doing something to Seamonkey until I read Mr. Francks comment.
KIS tech support advised that Seamonkey was not among the officially
supported browsers with KIS 2014 but that I should note Seamonkey.exe in
the KIS 'exclusions' list as a 'trusted application'. No explanation
was provided as to exactly why this might be necessary given Seamonkey's
Firefox lineage. Whatever, this solution worked and it apparently does
not interfere with KIS' security functions.
This has been an interesting education for me and my thanks to everyone
who provided comments about any aspect of the issue.
Henrik, perhaps if the next time you, or anyone else, is speaking with
the Kaspersky tech support people, you mentioned that SeaMonkey Suite is
the continuation of the Mozilla Suite, from which Firefox branched, and
that both Firefox and SeaMonkey (and other browsers) are based on the
Gecko engine (http://geckoisgecko.org/), maybe they can save themselves,
and their users, some trouble by "looking" for Gecko rather than Firefox!!
Might not accomplish anything, but you never know!!
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101
Firefox/29.0 SeaMonkey/2.26 Build identifier: 20140415200419
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101
SeaMonkey/2.26 Build identifier: 20140408191805
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
