LWN: Comments on "Macro virus for Staroffice discovered (Techworld)" https://lwn.net/Articles/185745/ This is a special feed containing comments posted to the individual LWN article titled "Macro virus for Staroffice discovered (Techworld)". en-us Fri, 12 Sep 2025 16:40:54 +0000 Fri, 12 Sep 2025 16:40:54 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Macro virus for Staroffice discovered (Techworld) https://lwn.net/Articles/185844/ https://lwn.net/Articles/185844/ Wol Why not just do it the WordPerfect way?<br> <p> AIUI, PerfectScript viruses are impossible. WordPerfect, despite having a pretty decent macro language, was immune to viruses until they licenced MS's VBA engine. And provided that engine isn't enabled, it's still immune :-)<br> <p> Cheers,<br> Wol<br> Thu, 01 Jun 2006 08:22:52 +0000 Macro virus for Staroffice discovered (Techworld) https://lwn.net/Articles/185831/ https://lwn.net/Articles/185831/ Arker Exactly. <br> <p> Expect more of this, not less, in the future, as so much FOSS 'desktop' software imitates bad proprietary software. <br> Thu, 01 Jun 2006 04:03:20 +0000 Macro virus for Staroffice discovered (Techworld) https://lwn.net/Articles/185830/ https://lwn.net/Articles/185830/ dwheeler ODF has some program-like capabilities defined (e.g., for graphs), but they are all strictly limited. The way the ODF spec is designed, I doubt there is a <i>requirement</i> that makes it impossible to be secure. Thu, 01 Jun 2006 04:01:18 +0000 Macro virus for Staroffice discovered (Techworld) https://lwn.net/Articles/185822/ https://lwn.net/Articles/185822/ Ross If the format dictates when the macro is executed and what it can do, it affects the security. That's my point. Otherwise it's an application bug/feature.<br> Thu, 01 Jun 2006 01:02:10 +0000 Macro virus for Staroffice discovered (Techworld) https://lwn.net/Articles/185821/ https://lwn.net/Articles/185821/ jhardin <font class="QuotedText">&gt; ... a fundamental weakness in the file format where, like with MS Office files, macros are allowed to ...</font><br> <p> What does the file format have to do with what macros are or are not allowed to do? The file format only stores the data; it's the *application* that supports a macro language, and allows it to run amok.<br> <p> Thu, 01 Jun 2006 00:35:03 +0000 Macro virus for Staroffice discovered (Techworld) https://lwn.net/Articles/185815/ https://lwn.net/Articles/185815/ Ross That would only work if it is taking advantage of a bug in a particular implementation. It could be (I have no idea) that there is a fundamental weakness in the file format where, like with MS Office files, macros are allowed to edit other files without prompting the user (the startup prompt is mostly useless because people get used to saying "Yes" on every file they open).<br> Wed, 31 May 2006 21:34:46 +0000 Macro virus for Staroffice discovered (Techworld) https://lwn.net/Articles/185804/ https://lwn.net/Articles/185804/ dwheeler I see no evidence that this virus can attack current systems. But if it could, one solution to virus propagation is diversity. If there were multiple ODF readers, it was <i>reasonable</i> for users to pick any one of them, <i>and</i> there was a virus attack that worked against one, it's less likely to work against others. <p> Oh look, there <i>are</i> multiple implementations, and the format is <i>designed</i> to encourage multiple interoperable implementations. Looks like ODF is the solution, not the problem. Wed, 31 May 2006 18:48:16 +0000 Macro virus for Staroffice discovered (Techworld) https://lwn.net/Articles/185750/ https://lwn.net/Articles/185750/ MortFurd Heise in Germany reported on the same "virus" and mentioned that Stardust only runs on StarOffice 5.<br> <p> StarOffice 8 is based on OOo 2, and StarOffice 7 was based on OOo 1. StarOffice 5 was out years ago. It was on the SuSE 6.2 CDs so many years ago when I switched from Windows 95 to SuSE 6.2.<br> <p> Heise does mention that Stardust could easily be ported to OOo 2, however.<br> Wed, 31 May 2006 14:51:25 +0000 Macro virus for Staroffice discovered (Techworld) https://lwn.net/Articles/185751/ https://lwn.net/Articles/185751/ grouch Too much imitation. Too much blurring of the line between a document and a program. Wed, 31 May 2006 14:50:40 +0000