Tim_Lopez
Tim_Lopez
gwm wrote:
And I beg this question:
How could such an issue as this not be found during initial product testing?? One would think...
..That.
This is a BIG flaw. It renders the software useless. Firewalls are there to insure privacy. When a guy cannot enter rules...
...the function of the firewall is moot.
Mark
Hi gwm,
I agree with you that this is an unacceptable experience, which is why I've committed the time I have to seeing that this issue gets resolved. I know there are a few Gurus that I've spoken with in person about this as well as people who have been on other internal discussions. We are taking this very seriously. I wish I could tell you more specifically about what we're doing and our progress on this, but I can't due to the proprietary confidential nature on the inner workings of the software. Just please know that I'm really fighting for everyone having this issue here. This issue will be addressed. 
The firewall can still function correctly as long as the Program Control window isn't launched. This would mean that new entries couldn't be added manually - they can be added if you select to block on the firewall popups. However, you should still be able to add them if Automatic Program Control is enabled (it would add them automatically). The issue isn't that the firewall can't handle so many rules - the issue is that it's having problems displaying all those rules.
Our QA has added the "test case" to test this exact scenario that caused this issue with future updates and versions so that once this issue is fixed it does not come back.
gwm wrote:And I beg this question:
How could such an issue as this not be found during initial product testing??
Simple really, they probably currently have no such test case. There testing would likely be on clean machines with everything on auto pilot. The vast majority of their customers run on auto pilot. That's the user base you have to keep happy.
The manual controls are a legacy feature that they thankfully have kept around. They just don't get allot of testing and are prone to breaking without anyone knowing about it right away. Even if I had beta tested 2012 I would have missed it. Its time consuming to test this particular case and I would have never spent the time to add 130+ programs to the list. I'm trying to come up with a way to automate it so I can test future releases.
The only reason I spent the time the other day trying to break it was first, to see if I could - because I was about to upgrade when I literally stumbled across this thread. Secondly, I wanted a test bed where I could try out any fixes that might be proposed. Lastly, because this particular feature is the most important feature of NIS for me.
Unfortunately, without automation, it will be time consuming to test 2013 too since we can't IMPORT the rules 
The legacy architecture might be such that importing and exporting rules is just too big of an obstacle for them. Security can't be the issue because we can import/export Identify Safe info - thankfully.
So I composed this before having to run off. I see that they will have a test case in the future for this scenario, that's great news!
Finally, thanks Tim for keeping the hope alive!
REF:
Hi Tim,
I fully understand that you cannot disclose much, and I do look forward to the patch. I was thrilled to see that you have responded.
To me it seems as if it took a complaint post on Facebook to get things rolling. We cannot see what goes on inside Symantec, so we can only assume we were being ignored, which surprised me because an error complaint of this magnitude should have been TOP PRIORITY since day one!
To support Norton/Symantec I would like to note that after watching a documentary--news clip about Symantecs Security Operations Center. I was so very impressed on how their main hub was built to be secure and function like Norad! This made me feel all warm and cozy inside knowing that my computer was being protected by this incredible resource. Those curious about this may like to see it for yourself and you can via a search term of -- Symantec Security Operations Center
With all of this said I am hopeful to see the patch come out very soon! I will continue to visit this thread to see if there have been any updates. Crossing my fingers to see something fixed within a few days, considerting what we pay for our subscriptions, and do not use pirated garbage we deserve a fix in a timely manner--
I am sure Symantec can afford to pay their programmers overtime 
- �1995 - 2013 Symantec Corporation Legal Notice License Agreement Privacy Policy Cookies Site Map RSS
