4 ms·
> Symantec says the theft actually occurred in 2006 So somebody stole the source code five years ago and they're starting to fix some of the glaring vulnerabil
by tga 15y ago
> Symantec says the theft actually occurred in 2006
So somebody stole the source code five years ago and they're starting to fix some of the glaring vulnerabilities today because this somehow got in the news?
That's reason enough to stay away from all network-enabled Symantec products, I would expect them to be equally insecure if this is the way they do things.
- jleader 15y agoThe key question here is, when did they become aware of the theft?
- dspillett 15y agoNo, the key issue is not fixing serious known (to them at least) security isses in the years they have been aware of them. Even if the code was never stolen at all, this to me is at very least a shocking lack of due diligence and at worst completely and utterly unprofessional ignorance of the importance of security (to the point where if I'd paid for that particular software in the last X years I'd be considering action to get a refund on the basis that the software was not fit for purpose).
- Urgo 15y agoDid it happen in 2006? I thought the 2006 version was what was stolen, but this happened just recently. EDIT: Never mind.. it did.. wow.. well supposedly nothing was released publicly until just now though. Someone was just sitting on it. Ex-employee?
- drivebyacct2 15y agoOr someone who has been making use of those holes for the past 5 years...
- dspillett 15y agoEven if the theft did happen yesterday, they had still been sitting on serious vulnerabilities for several years.