Time for a little conspiracy, but it has some Truth, well to be honest, it’s only truth. It seems that norton has a strange file that is trying to acces the internet without you telling it.
Pifts.exe
Then start googling it and you come accross some links to invalid Norton posts, it seems that norton deletes everything that is about pifts.exe
example = [url=http://community.norton.com/norton/board/message?board.id=nis_feedback&message.id=38010&jump=true#M38010]http://community.norton.com/norton/board/m...ump=true#M38010[/url]
Haha! Am I the only one being greeted by a kind “The Forums Are Closed For Maintenance” over at Norton’s forums? Good one. Although I did notice earlier that they were being bombarded with posts related to this “pifts.exe”, so their servers might actually be down or something.
The whole thing is a reversed text book example of good crisis management.
Whatever this is all about Symantic will need to respond somehow. If their forum site(s) are being overwhelmed then they may “float” a news story to the media (industry and public). Be on the watch for that.
I don’t thin their forums are floated. Don’t you think that Norton will have a bit of prevention. I like it how this guys says it. (and it’s probably gonna happen)
JerryYelserp wrote:
Okay, here's my prediction.
1) This was an "inside" job by an unhappy Symantec employee
2) He/She put the PIFTS code in a recent update
3) Then He/She hacked into the forum and set a code to delete all posts about the subject
Norton/Symantec couldn’t be so stupid as to delete their forum posts on purpose. That’s more damaging than having someone hack their code. Someone on the inside wanted to get back and hacked two seperate systems. I’m looking forward to learning the real story.
Here’s another nice reply, now is this real or not ?
Youri said...
From what I understand it seems to be some kind of a virus that is linked to terrorism. If you disassemble it you can see that the IP it connects is in northern africa. A cyber attack may be imminent. Back up your data, folks.
But you can’t say it’s positive … Remember that you’re in the Security branche, and that such failures are (mostly) not accepted… (except from Symantec mostly)
If they say the right stuff Iam shure that this new file could mean a good thing… Symantec goes official explains this, BAM all mags write the follow up story, and the publicity turns good again and more people get to hear about norton… =)
JerryYelserp wrote:
Okay, here's my prediction.
1) This was an "inside" job by an unhappy Symantec employee
2) He/She put the PIFTS code in a recent update
3) Then He/She hacked into the forum and set a code to delete all posts about the subject
Norton/Symantec couldn’t be so stupid as to delete their forum posts on purpose. That’s more damaging than having someone hack their code. Someone on the inside wanted to get back and hacked two seperate systems. I’m looking forward to learning the real story.
JerryYelserp wrote:
Okay, here's my prediction.
1) This was an "inside" job by an unhappy Symantec employee
2) He/She put the PIFTS code in a recent update
3) Then He/She hacked into the forum and set a code to delete all posts about the subject
Norton/Symantec couldn’t be so stupid as to delete their forum posts on purpose. That’s more damaging than having someone hack their code. Someone on the inside wanted to get back and hacked two seperate systems. I’m looking forward to learning the real story.
Maby that theory is correct, guess we get some info tomorrow. Still I find it weird that there has not been any official statements about this. Guess they are too busy doing those 5 minutes virus updates at the moment.
Even the most stupid idea, could be right Rag. Btw, it’s nice to hear from you :-La
Who I’m asking ? Who has this pic as an avatar ?
Maby that theory is correct, guess we get some info tomorrow. Still I find it weird that there has not been any official statements about this. Guess they are too busy doing those 5 minutes virus updates at the moment.
It seems that they're to busy deleting posts from it on there forum instead of fixing this ...
