Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
I think I understand the question now. Are you asking what is updated with "Symantec Shared Components - Norton Product Update"? Many of our Consumer (Norton) products and Enterprise products share components, which are aptly named Shared Components. This is an update to the Symantec Shared Components of your Norton Product.
Hi Floating_Red,
I'm uncertain about the reason for your question - no disrespect intended.
The short answer is that many Symantec products share code modules. These shared code modules need to be stored somewhere - and it makes sense to store them together (physically and logically) for simplicity sake. In reality, the modules could be stored anywhere on the drive so long as pointers addressed them correctly.
You are looking at an example of object oriented software techniques.
Code sharing (modularization) provides material benefits for end users as well as developers. Object oriented modules can be designed, tested and signed off for deployment. Code modules send messages to each other by a variety of means. Similarly, they may take advantage of existing code provided by microsoft through windows application progamming interfaces (API's)
This is a superficial smattering for anyone who might be interested.
Object oriented ideas date back to the early 1960's. Simula arrived in the late 1960's - object oriented programming was given legs. Around this period the Object Management Group (OMG) put out a call for a standard object modelling language. Over the years UML (unified modelling language) unified the work of two leading methodologisits Booch & Rumbaugh at Rational Corporation. Their work was accepted by the put to the OMG and the rest is history. We are now at UML 2.2. Welcome tomodelling analysis and design (MAD) and object oriented programming (OOP) and common object request broker architecture (CORBA). (Source: QUT Intro to Modelling Analysis and Design)
Before the introduction of these techniques, the overwhelming majority of software projects failed (source: Standish Chaos Report 2003. As of 2003, citing major improvements, a staggering 34% of projects were 'successful'. Please read the article and yes, the figure is correct: 34% success was something boastworthy especially coming from a parlous base position of 14%.
I'm touched across some fairly heavy duty subject matter ... If anyone is interested in the big picture by all means follow the trails I set out.
As far as the Shared Components used by Symantec - nothing sinister. You are watching best practice techniques in action qualified by the commercial reality. It is difficut to argue the merit of a particular deployment methology if you cannot turn a profit from your work.
Microsoft and all other software developers apply the same techniques because they work well. If you take a look at the Windows API, for example, you get a glimps of a small aspect of the issue that you raised.
HTH ...
Tony_Weiss wrote:I think I understand the question now. Are you asking what is updated with "Symantec Shared Components - Norton Product Update"? Many of our Consumer (Norton) products and Enterprise products share components, which are aptly named Shared Components. This is an update to the Symantec Shared Components of your Norton Product.
Message Edited by Tony_Weiss on 07-17-2008 08:47 PM
The Update Updates it to the most-current Version?
So, what are the "Updates Firewall configuration" (Symantec Trusted Application List)? I take it that that Update Updates the Firewall Rules Auto-Block?
Floating_Red wrote:
Tony_Weiss wrote:I think I understand the question now. Are you asking what is updated with "Symantec Shared Components - Norton Product Update"? Many of our Consumer (Norton) products and Enterprise products share components, which are aptly named Shared Components. This is an update to the Symantec Shared Components of your Norton Product.
Message Edited by Tony_Weiss on 07-17-2008 08:47 PM
The Update Updates it to the most-current Version?
So, what are the "Updates Firewall configuration" (Symantec Trusted Application List)? I take it that that Update Updates the Firewall Rules Auto-Block?
Message Edited by Floating_Red on 07-18-2008 12:57 PMMessage Edited by Floating_Red on 07-18-2008 01:10 PM
Hi,
It would help if you provided some context for your question. Something (involving the common shared files and liveupdate) has happened or not happend that caught your attention. Do you have a screen shot or log snippit that might help shed light on your question?
Your follow-up comments did not help me understand where you were going. Unless I'm wildly mistaken,when (if) lifeupdate 'updates' the firewall configuration then it *should* update all of the sub-classes and related object classes which fall under firewall configuration (rules, settings etc). In other words, the answer *should* be the update includes all objects of the Symantec products on your system. They may vary from installation to installation. It follows that the first part of your question is seemingly self explanatory. The second - yes.
I've always interpretted the term "Symantec Trusted Applications List" to have at least two and perhaps three states: safe / unsafe / unknown. Tech support might shed more light but I'd be surprised they give away much of anything in this security sensistive area.
The more technical issues you touch on would appear to be beyond most casual users and involve security concerns that most company's would prefer to keep quiet.
Perhaps the following may help you?
I took this from my LU log:
15/07/2008, 23:13:44 GMT -> EVENT - PRODUCT UPDATE SUCCEEDED EVENT - Update available for Symantec Trusted Application List - 2.1 - English. Update for ALESEQUENCE takes product from update 2008012200 to 2008062600. Server name - liveupdate.symantecliveupdate.com, Update file - 1214809388jtun_enfwcful.371, Signer - cn=Symantec Corporation,ou=Usage - spr1sgnwebpin01 token,ou=Locality - Springfield,ou=Product Group - LiveUpdate,ou=SymSignature,o=Symantec Corporation, package install code 0. The Update executed with a result code of 1800, => Success
And this:
15/07/2008, 23:31:34 GMT -> LiveUpdate is about to launch a new callback proxy process for product Symantec Trusted Application List with moniker {1329A6C6-002D-475b-9AEB-F85CB19E4266}.
The Symantec tech folk can correct me if I'm wrong. Liveupdate seems to be a "client" program that works with an enterprise server (somewhere) with Symantec. Cycling through each Symantec application, it compares the installed profile against a list on the server. We know that certain updates can be withheld given our experience with 15.0 to 15.5
The snippet from the log appears to be a records (comma delimited perhaps). The first involved "Symantec Trusted Application List"
These entries appear to denote the progress of a script - checking internal values (checksums perhaps?) with a shopping list of 'latest files'. The top snippitends with a success token - suggesting that ifit failed then, depending upon the significance / cause of the problem it might trigger the general error trapping module: it yells at you :)
Sorry ... doubt I've advanced your concern.
1. Norton entfernen, am besten mit den Removal tool
http://www.norton.com/symnrt
2. Rechner neustarten
3. Norton von der ofiziellen Seite installieren.
http://www.norton.de/nav11
achten Sie bitte auf den Pop Up Blocker der den Download blockieren könnte
Für weitere Hilfe können Sie sich das Installationsvideo anschauen, hier wird Ihnen alles Schritt für Schritt beschrieben :
http://www.symantec.com/de/de/norton/support/Herunterladen-von-Norton-Produkten.jsp
------------------------------------------------------------------------------------------------------------------------------------------------
Eine Sitzung mit den Chat Support wird diesen Fehler bestimmt aus der Welt schaffen, www.norton.com/chat
Der Chat Support ist montags bis freitags von 9:00 bis 20:00 Uhr erreichbar.
mine just updated last night. hopefully yours will soon. just run live update every so often.
Bob_Eyster wrote:So far I'm not seeing the 20.2.1.22 update and the Norton Updat Center says I am up-to-date with 20 2.0.19
See Tim Lopez's post about the update here http://community.norton.com/t5/Norton-360/Product-Update-20-2-1-of-Norton-360/m-p/891497#U891497
Note that it is a phased rollout, so it may depend on where you are located.