Thank you very much, the Kaspersky Labs analyst and other virus naming companies experts for finding it and calling it "virus," "proof of concenpt," "Virus.StarOffice.Stardust.a," "SBasic.Stardust.A!int," "XML_DUSTAR.A," "StarDust.intd," whatever.
Thank you, we learned a lot about viruses, macro viruses and proof of concept viruses.
We love to see Our conclusions, opinions and OOoDust.
1. OpenOffice.org Team's announcement and conclusion:
"it is not even a virus" "users should never accept files from unknown sources"
2. David Fraser's conclusion:
"this is all nothing to be afraid of"
3. Pavel Janik's conclusion:
"just remove it from your system"
4. Malte Timmermann's conclusion:
"This is not a virus, even not a proof of concept"
5. John McCreesh's conclusion:
"if we are relying on these 'anti-virus experts' to protect the IT industry from viruses, then the sooner everyone moves to open-source software the better. At least then we can judge who the real experts are"
6. Pavel Janik's opinion:
"the blogger from Kaspersky simply should have contacted OpenOffice.org security team first, not only because it is "standard way" to report security issues to vendors but it could also prevent everyone from this faux pas"
7. Laurent Godard's "proof of nothing," OOoDust
"OpenOffice.org project has a structure for reporting any suspicious behaviour, so feel free to contact us"
OpenOffice.org security team: http://www.openoffice.org/security/
