Frank Wein wrote:
Justin Wood (Callek) wrote:
Hey Guys,
So I have to say, I am quite annoyed with Symantec/Norton at the moment.
Our Beta 2, which has been out for ~ a week, and I submitted the
whitelist request to Norton ~12 hours before the *DAY* of our release,
still is not complete.
With the release cadence we have/need, the turnaround time on their
whitelisting is completely unacceptable/bad. It completely hurts our
ability to get meaningful data for betas, and hurts our ability to keep
our release users up to date with latest stability/security updates.
My proposal:
* No longer wait for Symantec to indicate that the whitelisting is complete
I agree with that.
* Mention it on our known-issues page that Norton can interact badly
with us on occassion
Yes.
* Specifically list the .dll's [by name] it thinks are viruses on our
known-issues page as "ok" and "Norton's fault"
Agreed.
* Continue to submit whitelisting requests ASAP
* Continue to move forward with getting signed builds out [`may` help
with this]
* Continue to *try* getting a human contact at Norton to see if/when we
can speed up their process or fix this misidentification, and how.
The key point is this *will* be a pain point for windows users who have
Norton, where the most-logical solution for those users is to *disable*
their Virus Software during the duration of SeaMonkey use. And is
specifically manifests in the following ways:
* Quarantines 1-or-2 dll's
* The dll's affect our cryptography ability, in such that them missing
may/could break some https sites from functioning/cause crashes etc. (I
haven't witnessed it, but I also have avoiding us ever shipping in this
case)
* Restoration of the dll's seems to sign/modify them slightly such that
partial updates fail for these users, and end up having to download
updates twice (the second download being our full 20ish MB download).
Hrm, too bad the failure case does not obviously point to Norton as a
cause of this. But after all the user should have already been notified
about a "virus" before.
What "virus" does Norton actually detect? Does Firefox also whitelist
their versions with Symantec? After all our builds should not be that
different as the NSS dlls (which do the encryption) use exactly the same
code as the Firefox ones.
Frank
There is another option which has been used by other software vendors in
the past, and continues today.
Create simple install/uninstall instructions on your download page.
These instructions should include:
1. With your current we browser download the installation package into a
folder of your choice.
2. After download is complete suggest the customer disconnect from the
internet.
3. Turn off Norton's Anti-virus.
4. Double click the downloaded file to install the new program.
5. After install of the new program/upgrade is complete suggest the
customer remove the older version.
6. After the install is complete have the new program/version open a web
page welcoming the customer to this new version, and reminding the
customer he/she should warm boot the computer, and double check that
Norton's is again live and well, manual re-connection to the internet
may be required. In many PC's rebooting will turn on previously turned
off manually selected programs, except Network Connections, and no
further action is necessary.
7. After rebooting The program can be launched in the usual manner, in
the case of a new installation some user settings may need to be
adjusted (supply a page to these settings). In the case of an upgrade
the new version should pick up the user settings from the named user
profile.
Important. Advise the user to double check the condition of the AV
program before connecting to the internet (icon in System Task Bar, next
to clock).
Michael G
--
Armadillo Web Development
www.armadilloweb.com
Cell: 903.244.3644
Opening your Door to Opportunity
and inviting the world to walk through.
Character is doing the right thing...
Even when no one is watching...
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
